[Kernel-packages] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
Thank you for reporting this bug to Ubuntu. Ubuntu Studio 18.04 (bionic) reached end-of-life on January 26, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Incomplete Status in rtirq package in Ubuntu: Invalid Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926597] Re: Linux 5.10.0-1024.25 breaks HDMI with Intel i915
Thanks for the update. I think using the HWE kernel is the best compromise for the interim. -- 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/1926597 Title: Linux 5.10.0-1024.25 breaks HDMI with Intel i915 Status in linux package in Ubuntu: Incomplete Bug description: Hi, [Thinkpad T480s, Intel iGPU 8550u, Ubuntu Focal up-to-date, GNOME Wayland session] Previous 5.10.0-1023.24 was ok. Kernel 5.8 HWE is ok. I did not test a X session. Plugging HDMI after GNOME is loaded fails to display anything on the HDMI display. Plugging HDMI at boot or at GDM screen makes the HDMI display works as usual. Unplugging HDMI (display only on this one) during GNOME session does not update displays state. Nothing happens. I have to press the switch-display-key on my laptop to actualize the setup and make my laptop's display active. When I unplug HDMI during GNOME session, nothing appears in logs. My laptop fails to enter sleep after having unplugged the HDMI. Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
Sorry that I forget the add the VID/PID to the hid quirk table. Could you help me verify the kernel in https://people.canonical.com/~mschiu77/lp1927545/v2? Thanks -- 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/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I found that some of the Lenovo Lenovo Essential Wireless Keyboard Fn keys don't work. First one is Mute mic (Fn+F4), second one is Scissors (Fn+F10, probably hotkey for Windows Snipping Tool for selective screenshot).gnome-control-panel, xev and evtest doesn't react on pressing these buttons. Here what I was able to get via sudo cat /dev/usb/hiddev0 | hexdump -v -e '/1 "%02X\n"' : For Mute key 00 00 00 FF DC 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 For Scissors 00 00 00 FF DB 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asudak 2085 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 6 22:36:50 2021 InstallationDate: Installed on 2021-04-13 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-18 (17 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910928] Re: Intel Killer AX1650i [8086:34f0] Subsystem [8086:0074] Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL
[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/1910928 Title: Intel Killer AX1650i [8086:34f0] Subsystem [8086:0074] Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL Status in linux package in Ubuntu: Expired Bug description: After I have installed the Ubuntu - I have noticed, that Bluetooth won't go turn on after Suspend. The only way to get it working - reboot the system. WiFi Adapter - AX201 I have tried the latest kernel (5.11.rc2) - no luck. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InterestingModules: rfcomm bnep btusb bluetooth LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20SL NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: bluez 5.55-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-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/18/2020 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN22WW dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 14-IIL dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL: dmi.product.family: Thinkbook 14-IIL dmi.product.name: 20SL dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL dmi.product.version: Lenovo ThinkBook 14-IIL dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:26:49:C4:B9:6C ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:19913 acl:0 sco:0 events:3169 errors:0 TX bytes:770617 acl:0 sco:0 commands:3167 errors:0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InterestingModules: rfcomm bnep btusb bluetooth LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20SL NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: bluez 5.55-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-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/18/2020 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN22WW dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 14-IIL dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL: dmi.product.family: Thinkbook 14-IIL dmi.product.name: 20SL dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL dmi.product.version: Lenovo ThinkBook 14-IIL dmi.sys.vendor: LENOVO hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910928/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927832] Re: [radeon] Static effect on HDMI out using kernel 5.11 and later (but 5.8.0-50-generic works)
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927832 Title: [radeon] Static effect on HDMI out using kernel 5.11 and later (but 5.8.0-50-generic works) Status in linux package in Ubuntu: Fix Released Bug description: lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 package version : kernel-image 5.11.0-16-generic what I expect to happen : to show my desktop correctly on second hdmi monitor what happens : static effect like shown in attached photo Since upgrade to hirsute (21.04) from groovy (20.10) my hdmi port on my graphic card stopped to work correctly and started to display static effect on second monitor, as you can see from the attached photo. Here it is mine videocards: Code: $ lspci | grep VGA 01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470] I was able to test it with 3 different kernels : Code: 5.12.1-051201-generic # last mainline kernel 5.11.0-16-generic # last official kernel from hirsute 5.8.0-50-generic # probably a old kernel still there from groovy Only the older one, 5.8.0-50-generic was working correctly with dual monitor with no issues. Kind regards ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,move,gnomecompat,vpswitch,place,grid,regex,session,snap,mousepoll,imgpng,resize,wall,animation,unitymtgrabhandles,expo,ezoom,fade,workarounds,scale,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 8 18:45:37 2021 DistUpgraded: 2021-04-22 22:22:18,672 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_proprietary.py”: Failed to execve: File o directory non esistente (1)) DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed virtualbox, 6.1.18, 5.8.0-50-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RS880M [Mobility Radeon HD 4225/4250] [103c:1441] Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470] [1002:68e0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Park [Mobility Radeon HD 5430/5450/5470] [103c:1441] InstallationDate: Installed on 2019-10-26 (560 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=a5324660-5421-487c-ad0f-b562bd39c622 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-04-22 (15 days ago) dmi.bios.date: 02/25/2013 dmi.bios.release: 15.41 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.29 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1441 dmi.board.vendor: Hewlett-Packard dmi.board.version: 67.33 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.ec.firmware.release: 103.51 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.29:bd02/25/2013:br15.41:efr103.51:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr059C1124301020100:rvnHewlett-Packard:rn1441:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.sku: XD610EA#ABZ dmi.product.version: 059C1124301020100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/192
[Kernel-packages] [Bug 1928950] Re: ThinkPad X250 boot failure with kernel 5.4.0-73-generic (Linux Mint 19.3)
First, let's ensure upstream kernel doesn't have this issue. So please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc5/amd64/ Headers are not 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/1928950 Title: ThinkPad X250 boot failure with kernel 5.4.0-73-generic (Linux Mint 19.3) Status in linux package in Ubuntu: Incomplete Bug description: Bug/Regression introduced between 5.4.0-73 and 5.4.0-72 (-72 and all previous kernels installed by Mint 19.3 had no problems). Happens whether docked or undocked. Might relate to Bug #1928530. System tells to do a journalctl -xb, but I couldn't spot if there's something relevant. I'll collect the logs twice to help find the difference (one from -73 panic shell and one from -72 normally booted). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929870] Re: AMD desktop often fails to resume from deep suspend
When the issue happens, does magic key works? Hold alt + printscreen, press S, U, B. -- 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/1929870 Title: AMD desktop often fails to resume from deep suspend Status in linux package in Ubuntu: Confirmed Bug description: Machine setup: Desktop PC Ubuntu 21.04 Linux version 5.11.0-17-generic AMD Ryzen 3900X Asus X590 PRIME PRO motherboard NVIDIA P400 GPU Approximately one in every 4 attempts to resume from a deep suspend fails. When the issue occurs the fans spin up but the monitor displays no output and input devices do not function, the system appears frozen and must be restarted using power or reset buttons. I have tried using different dNVIDIA isplay drivers (proprietary as well as open source) as well as trying an AMD Radeon HD 6450 GPU instead of the NVIDIA GPU. I have tried the following kernel parameters: processor.max_cstate=1 rcu_nocbs=0-23 I have updated the BIOS several times. I had similar problems with Ubuntu 20.10. I have enabled some additional kernel logging with initcall_debug. Fairly consistently the last message printed in the kernel log is from the ethernet driver: May 27 09:19:43 jacob-tm kernel: [ 230.878348] OOM killer enabled. May 27 09:19:43 jacob-tm kernel: [ 230.878349] Restarting tasks ... May 27 09:19:43 jacob-tm kernel: [ 230.879023] usb 5-2.3: USB disconnect, device number 4 May 27 09:19:43 jacob-tm kernel: [ 230.879026] usb 5-2.3.1: USB disconnect, device number 5 May 27 09:19:43 jacob-tm kernel: [ 230.879285] done. May 27 09:19:43 jacob-tm kernel: [ 230.879318] PM: suspend exit May 27 09:19:43 jacob-tm kernel: [ 230.880916] rfkill: input handler enabled May 27 09:19:43 jacob-tm kernel: [ 230.955727] kauditd_printk_skb: 1 callbacks suppressed May 27 09:19:43 jacob-tm kernel: [ 230.955731] audit: type=1400 audit(1622132383.424:64): apparmor="DENIED" operation="capab le" profile="/usr/sbin/cupsd" pid=4418 comm="cupsd" capability=12 capname="net_admin" May 27 09:19:43 jacob-tm kernel: [ 230.966192] audit: type=1400 audit(1622132383.432:65): apparmor="DENIED" operation="capab le" profile="/usr/sbin/cups-browsed" pid=4429 comm="cups-browsed" capability=23 capname="sys_nice" May 27 09:19:43 jacob-tm kernel: [ 231.120385] rfkill: input handler disabled May 27 09:19:43 jacob-tm kernel: [ 231.225924] usb 5-2.3.2: USB disconnect, device number 6 May 27 09:19:43 jacob-tm kernel: [ 231.481893] usb 5-2.3.5: USB disconnect, device number 7 May 27 09:19:47 jacob-tm kernel: [ 235.009576] igb :05:00.0 enp5s0: igb: enp5s0 NIC Link is Up 1000 Mbps Full Duplex, Fl ow Control: RX/TX May 27 09:19:47 jacob-tm kernel: [ 235.009913] IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-17-generic 5.11.0-17.18 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacob 2024 F pulseaudio /dev/snd/controlC0: jacob 2024 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 27 14:12:33 2021 InstallationDate: Installed on 2020-10-28 (211 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp5s0no wireless extensions. docker0 no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=f721d5df-ceec-434a-919a-0680ee380996 ro quiet splash initcall_debug processor.max_cstate=1 rcu_nocbs=0-23 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-17-generic N/A linux-backports-modules-5.11.0-17-generic N/A linux-firmware 1.197 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-14 (13 days ago) dmi.bios.date: 05/08/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3604 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3604:bd05/08/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP
[Kernel-packages] [Bug 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
This bug was fixed in the package nvidia-settings - 460.73.01-0ubuntu0.21.04.1 --- nvidia-settings (460.73.01-0ubuntu0.21.04.1) hirsute; urgency=medium * New upstream release (LP: #1925522). -- Alberto Milone Thu, 13 May 2021 11:52:30 +0200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Released Status in fabric-manager-460 source package in Bionic: Fix Released Status in libnvidia-nscq-450 source package in Bionic: Fix Released Status in libnvidia-nscq-460 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in fabric-manager-450 source package in Focal: Fix Released Status in fabric-manager-460 source package in Focal: Fix Released Status in libnvidia-nscq-450 source package in Focal: Fix Released Status in libnvidia-nscq-460 source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-465 source package in Focal: Fix Released Status in nvidia-settings source package in Focal: Fix Released Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Released Status in fabric-manager-450 source package in Hirsute: Fix Released Status in fabric-manager-460 source package in Hirsute: Fix Released Status in libnvidia-nscq-450 source package in Hirsute: Fix Released Status in libnvidia-nscq-460 source package in Hirsute: Fix Released Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Released Status in nvidia-settings source package in Hirsute: Fix Released Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450 series to the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 450-server == * New upstream release (LP: #1925522). - Fixed an issue with the NSCQ library that caused clients such as DCGM t
[Kernel-packages] [Bug 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
This bug was fixed in the package nvidia-settings - 460.73.01-0ubuntu0.20.10.1 --- nvidia-settings (460.73.01-0ubuntu0.20.10.1) groovy; urgency=medium * New upstream release (LP: #1925522). * debian/patches/08_add_prime_support.patch: - Stop the timeout after the child is done. This fixes an error that g_type_check_instance_is_a() was throwing. -- Alberto Milone Wed, 05 May 2021 15:32:25 +0200 ** Changed in: nvidia-settings (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Released Status in fabric-manager-460 source package in Bionic: Fix Released Status in libnvidia-nscq-450 source package in Bionic: Fix Released Status in libnvidia-nscq-460 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in fabric-manager-450 source package in Focal: Fix Released Status in fabric-manager-460 source package in Focal: Fix Released Status in libnvidia-nscq-450 source package in Focal: Fix Released Status in libnvidia-nscq-460 source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-465 source package in Focal: Fix Released Status in nvidia-settings source package in Focal: Fix Released Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Released Status in fabric-manager-450 source package in Hirsute: Fix Released Status in fabric-manager-460 source package in Hirsute: Fix Released Status in libnvidia-nscq-450 source package in Hirsute: Fix Released Status in libnvidia-nscq-460 source package in Hirsute: Fix Released Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Released Status in nvidia-settings source package in Hirsute: Fix Released Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450 series to the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, t
[Kernel-packages] [Bug 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
This bug was fixed in the package nvidia-settings - 460.73.01-0ubuntu0.20.04.1 --- nvidia-settings (460.73.01-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1925522). * debian/patches/08_add_prime_support.patch: - Stop the timeout after the child is done. This fixes an error that g_type_check_instance_is_a() was throwing. -- Alberto Milone Wed, 05 May 2021 15:41:06 +0200 ** Changed in: nvidia-settings (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Released Status in fabric-manager-460 source package in Bionic: Fix Released Status in libnvidia-nscq-450 source package in Bionic: Fix Released Status in libnvidia-nscq-460 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in fabric-manager-450 source package in Focal: Fix Released Status in fabric-manager-460 source package in Focal: Fix Released Status in libnvidia-nscq-450 source package in Focal: Fix Released Status in libnvidia-nscq-460 source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-465 source package in Focal: Fix Released Status in nvidia-settings source package in Focal: Fix Released Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Released Status in fabric-manager-450 source package in Hirsute: Fix Released Status in fabric-manager-460 source package in Hirsute: Fix Released Status in libnvidia-nscq-450 source package in Hirsute: Fix Released Status in libnvidia-nscq-460 source package in Hirsute: Fix Released Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Released Status in nvidia-settings source package in Hirsute: Fix Released Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450 series to the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the
[Kernel-packages] [Bug 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
This bug was fixed in the package nvidia-settings - 460.73.01-0ubuntu0.18.04.1 --- nvidia-settings (460.73.01-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream release (LP: #1925522). * debian/patches/08_add_prime_support.patch: - Stop the timeout after the child is done. This fixes an error that g_type_check_instance_is_a() was throwing. -- Alberto Milone Wed, 05 May 2021 15:48:47 +0200 ** Changed in: nvidia-settings (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: nvidia-settings (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Released Status in fabric-manager-460 source package in Bionic: Fix Released Status in libnvidia-nscq-450 source package in Bionic: Fix Released Status in libnvidia-nscq-460 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in fabric-manager-450 source package in Focal: Fix Released Status in fabric-manager-460 source package in Focal: Fix Released Status in libnvidia-nscq-450 source package in Focal: Fix Released Status in libnvidia-nscq-460 source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-465 source package in Focal: Fix Released Status in nvidia-settings source package in Focal: Fix Released Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Released Status in fabric-manager-450 source package in Hirsute: Fix Released Status in fabric-manager-460 source package in Hirsute: Fix Released Status in libnvidia-nscq-450 source package in Hirsute: Fix Released Status in libnvidia-nscq-460 source package in Hirsute: Fix Released Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Released Status in nvidia-settings source package in Hirsute: Fix Released Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450 series to the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this
[Kernel-packages] [Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
We're still waiting on verification for Groovy - the kernel task was verified, but the groovy build of crash has not been verified yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL Status in crash package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in crash source package in Bionic: Fix Committed Status in linux source package in Bionic: Invalid Status in crash source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in crash source package in Groovy: Fix Committed Status in linux source package in Groovy: Fix Released Bug description: [Impact] On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility 7.2.8-1ubuntu0.18.04 fails with: crash: cannot determine VA_BITS_ACTUAL This bug has been addressed upstream and needed patches both in crash and kernel. Kernel patch : commit bbdbc11804ff0b4130e7550113b452e96a74d16e Author: Bhupesh Sharma Date: Thu May 14 00:22:37 2020 +0530 arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo Crash patch : commit 1c45cea02df7f947b4296c1dcaefa1024235ef10 Author: Bhupesh Sharma Date: Tue Jul 14 01:14:49 2020 +0530 arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ Series affected : Kenrel : This affects Focal (5.4 kernel) and Groovy (5.8 kernel). Hirsute already contains the commit and kernels prior to 5.3 are not affected. Crash : The commit is already in Hirsute. Groovy, Focal and Bionic are affected. In case of Bionic the bug appears only if 5.4 hwe kernel is used. [Test Case] On an arm64 host which runs the affected releases and kernels after creating a crashdump try to open it with crash. It will fail with : crash: cannot determine VA_BITS_ACTUAL [Where problems could occur] Kernel patch : The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ variable in vmcoreinfo. Given that this is a simple operation and that this patch landed upstream in 5.9 and no regressions have been reported, it is safe to assume that the regression potential is minimal. Any potential problem would occur in vmcoreinfo since this is where TCR_EL1.T1SZ variable is exported. Crash patch : This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible with the kernel change above for crash to be able to read it. The regression potential is small and any problem would regard reading this variable. [Other] Workaround : This bug/change in crash provides a workaround for 5.4+ https://github.com/crash-utility/crash/issues/52 kernels. While it appears as though it this was fixed it https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still doesn't seem to work with a 5.4 kernel including. I also tested https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb and it exhibits the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926548] Re: The gatt protocol has out-of-bounds read that leads to information leakage
** Also affects: bluez via
https://github.com/bluez/bluez/issues/70
Importance: Unknown
Status: Unknown
** Tags added: fixed-in-5.56 fixed-upstream
** Also affects: bluez (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu Hirsute)
Status: New => Fix Released
** Changed in: bluez (Ubuntu Impish)
Status: New => Fix Released
** Tags added: rls-ff-incoming
--
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/1926548
Title:
The gatt protocol has out-of-bounds read that leads to information
leakage
Status in Bluez Utilities:
Unknown
Status in bluez package in Ubuntu:
Fix Released
Status in bluez source package in Hirsute:
Fix Released
Status in bluez source package in Impish:
Fix Released
Bug description:
I installed the latest bluez 5.53-0ubuntu3 version using apt-get install. It
seems that this vulnerability was silently fixed in the latest bluez5.8, and
the cve number was not assigned.
But this vulnerability now affects the latest ubuntu system
This vulnerability allows an attacker to remotely obtain most of the contents
of the heap without authentication.
The vulnerability code is stored in cli_feat_read_cb, this function does not
verify the offset parameter
The vulnerability code is as follows
gatt-database.c
1054：static void cli_feat_read_cb(struct gatt_db_attribute *attrib,
unsigned int id, uint16_t offset,
uint8_t opcode, struct bt_att *att,
void *user_data){
...
len = sizeof(state->cli_feat)-offset;
value = len? &state->cli_feat[offset]: NULL;
done:
gatt_db_attribute_read_result(attrib, id, ecode, value, len);
}
len will become very large due to integer overflow, so that a message of mtu
(0x90) size will be sent later
The message content is the buffer pointed to by value, which can be most
addresses on the heap
poc is very simple, the core is this line of code
memcpy(&buf[0],"\x0c\x0b\x00\x0d\x00",5);
0xc stands for read
\x0b\x00 represents the handle of the client feature, which can be obtained
through the find info message, which seems to be 0b by default
\x0d\x00 is offset0xd
this vulnerability is serious
I want to apply for a cve number, although this has been silently fixed in
the latest version
To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1926548/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926548] Re: The gatt protocol has out-of-bounds read that leads to information leakage
** Information type changed from Private Security to Public Security
--
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/1926548
Title:
The gatt protocol has out-of-bounds read that leads to information
leakage
Status in bluez package in Ubuntu:
New
Bug description:
I installed the latest bluez 5.53-0ubuntu3 version using apt-get install. It
seems that this vulnerability was silently fixed in the latest bluez5.8, and
the cve number was not assigned.
But this vulnerability now affects the latest ubuntu system
This vulnerability allows an attacker to remotely obtain most of the contents
of the heap without authentication.
The vulnerability code is stored in cli_feat_read_cb, this function does not
verify the offset parameter
The vulnerability code is as follows
gatt-database.c
1054：static void cli_feat_read_cb(struct gatt_db_attribute *attrib,
unsigned int id, uint16_t offset,
uint8_t opcode, struct bt_att *att,
void *user_data){
...
len = sizeof(state->cli_feat)-offset;
value = len? &state->cli_feat[offset]: NULL;
done:
gatt_db_attribute_read_result(attrib, id, ecode, value, len);
}
len will become very large due to integer overflow, so that a message of mtu
(0x90) size will be sent later
The message content is the buffer pointed to by value, which can be most
addresses on the heap
poc is very simple, the core is this line of code
memcpy(&buf[0],"\x0c\x0b\x00\x0d\x00",5);
0xc stands for read
\x0b\x00 represents the handle of the client feature, which can be obtained
through the find info message, which seems to be 0b by default
\x0d\x00 is offset0xd
this vulnerability is serious
I want to apply for a cve number, although this has been silently fixed in
the latest version
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926548/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930976] Re: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
Hi, I solved it by reimaged with xubuntu 20.04 kernel 5.8.043 and it works better than 5.8.053 and 5.8.055. So, I wish to keep this kernel on the GRUB for longer-term or I want to keep more than 2 available kernels on the GRUB bootloader. IS it possible? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930976 Title: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers Status in linux-hwe-5.8 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Kernel: 5.8.0-55 The last kernel destroyed my Ubuntu 20.04.02 installation, something went wrong with some kernel packages. It seems like Ubuntu is unable to find my video card correctly and the device drivers from Nvidia don't seem to work anymore. I had to do a clean installation, but even that doesn't solve the problem. I think this is a serious issue that needs to be looked into. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jun 5 16:50:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation Device [10de:2206] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:403f] InstallationDate: Installed on 2021-06-05 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=4984fe2f-d45f-4734-884c-2426bcf10ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33j dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33j:bd04/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1930976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
In my case with Parrot Linux it was a case of Interrupt conflicts. IRQ#18 kept being disabled by the system. After disabling the EHCI Handoff in the BIOS,ehci_hcd:usb1 was replaced with ehci_hcd:usb2 and the mouse lag after a random period of time stopped. You can view your interrupt assignments with: cat /proc/interrupts Mine changed from: 18: IO-APIC 18-fasteoi ehci_hcd:usb1, pata_jmicron, ata_piix, uhci_hcd:usb8 to: 18: IO-APIC 18-fasteoi ehci_hcd:usb2, pata_jmicron, ata_piix, uhci_hcd:usb8 And the problem was resolved. -- 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/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Confirmed Status in rtirq package in Ubuntu: Invalid Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931239] Re: System crash regulary
Thanks for the bug report. Those look like a few different unrelated kernel crashes. This usually happens when there is a faulty RAM module so please use these tools to do a full health check of the system memory: https://www.memtest.org/ https://www.memtest86.com/ It will take several hours so you will need to leave it running overnight. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931239 Title: System crash regulary Status in linux package in Ubuntu: Incomplete Bug description: I saw the following error in the kernel log (kern.log) directly after the crash occurred. I was watching my system with a tail -f kern.log on a remote shell. --- Jun 8 11:29:56 workstation kernel: [49956.666945] general protection fault, probably for non-canonical address 0xe365a4770fa8af10: [#1] SMP NOPTI Jun 8 11:29:56 workstation kernel: [49956.666958] CPU: 8 PID: 706155 Comm: git Tainted: G IOE 5.11.0-18-generic #19-Ubuntu Jun 8 11:29:56 workstation kernel: [49956.666966] Hardware name: Dell Inc. Precision 5820 Tower X-Series/0X75JG, BIOS 2.2.0 04/14/2020 Jun 8 11:29:56 workstation kernel: [49956.666969] RIP: 0010:__kmalloc+0xb2/0x250 Jun 8 11:29:56 workstation kernel: [49956.666983] Code: 83 72 63 49 8b 00 49 83 78 10 00 48 89 45 c0 0f 84 85 01 00 00 48 85 c0 0f 84 7c 01 00 00 41 8b 4c 24 28 49 8b 3c 24 48 01 c1 <48> 8b 19 48 89 ce 49 33 9c 24 b8 00 00 00 48 8d 4a 01 48 0f ce 48 Jun 8 11:29:56 workstation kernel: [49956.666989] RSP: :ae48650b7878 EFLAGS: 00010282 Jun 8 11:29:56 workstation kernel: [49956.666996] RAX: e365a4770fa8aee0 RBX: RCX: e365a4770fa8af10 Jun 8 11:29:56 workstation kernel: [49956.667000] RDX: 00044185 RSI: 0d40 RDI: 000310c0 Jun 8 11:29:56 workstation kernel: [49956.667004] RBP: ae48650b78c0 R08: 9f9c9fa310c0 R09: 0001 Jun 8 11:29:56 workstation kernel: [49956.667008] R10: 0001 R11: R12: 9f8d40043a00 Jun 8 11:29:56 workstation kernel: [49956.667012] R13: 0060 R14: 9f8d40043a00 R15: 0d40 Jun 8 11:29:56 workstation kernel: [49956.667016] FS: 7f2038755f80() GS:9f9c9fa0() knlGS: Jun 8 11:29:56 workstation kernel: [49956.667021] CS: 0010 DS: ES: CR0: 80050033 Jun 8 11:29:56 workstation kernel: [49956.667024] CR2: 7f2038a1c000 CR3: 0002ac41e004 CR4: 003726e0 Jun 8 11:29:56 workstation kernel: [49956.667029] DR0: DR1: DR2: Jun 8 11:29:56 workstation kernel: [49956.667032] DR3: DR6: fffe0ff0 DR7: 0400 Jun 8 11:29:56 workstation kernel: [49956.667036] Call Trace: Jun 8 11:29:56 workstation kernel: [49956.667039] ? ext4_find_extent+0x381/0x450 Jun 8 11:29:56 workstation kernel: [49956.667051] ext4_find_extent+0x381/0x450 Jun 8 11:29:56 workstation kernel: [49956.667058] ext4_ext_map_blocks+0x72/0x980 Jun 8 11:29:56 workstation kernel: [49956.667064] ? find_get_entry+0xcd/0x160 Jun 8 11:29:56 workstation kernel: [49956.667073] ? find_get_entry+0xcd/0x160 Jun 8 11:29:56 workstation kernel: [49956.667080] ? ext4_es_lookup_extent+0x164/0x210 Jun 8 11:29:56 workstation kernel: [49956.667087] ext4_map_blocks+0x261/0x590 Jun 8 11:29:56 workstation kernel: [49956.667093] ? xas_load+0x9/0x80 Jun 8 11:29:56 workstation kernel: [49956.667103] ? xa_load+0x61/0x90 Jun 8 11:29:56 workstation kernel: [49956.667110] ext4_mpage_readpages+0x533/0xa70 Jun 8 11:29:56 workstation kernel: [49956.667118] ? __mod_lruvec_state+0x3a/0x50 Jun 8 11:29:56 workstation kernel: [49956.667127] ext4_readahead+0x33/0x40 Jun 8 11:29:56 workstation kernel: [49956.667132] read_pages+0x89/0x270 Jun 8 11:29:56 workstation kernel: [49956.667140] page_cache_ra_unbounded+0x137/0x1f0 Jun 8 11:29:56 workstation kernel: [49956.667147] do_page_cache_ra+0x3d/0x40 Jun 8 11:29:56 workstation kernel: [49956.667152] do_sync_mmap_readahead+0x10d/0x1c0 Jun 8 11:29:56 workstation kernel: [49956.667159] filemap_fault+0x571/0x840 Jun 8 11:29:56 workstation kernel: [49956.667166] ? xas_find+0x17a/0x1d0 Jun 8 11:29:56 workstation kernel: [49956.667172] ? filemap_map_pages+0x215/0x3f0 Jun 8 11:29:56 workstation kernel: [49956.667179] ext4_filemap_fault+0x32/0x50 Jun 8 11:29:56 workstation kernel: [49956.667185] __do_fault+0x3c/0xe0 Jun 8 11:29:56 workstation kernel: [49956.667194] do_fault+0xc4/0x1f0 Jun 8 11:29:56 workstation kernel: [49956.667201] handle_pte_fault+0x1e5/0x260 Jun 8 11:29:56 workst
[Kernel-packages] [Bug 1931239] [NEW] System crash regulary
You have been subscribed to a public bug: I saw the following error in the kernel log (kern.log) directly after the crash occurred. I was watching my system with a tail -f kern.log on a remote shell. --- Jun 8 11:29:56 workstation kernel: [49956.666945] general protection fault, probably for non-canonical address 0xe365a4770fa8af10: [#1] SMP NOPTI Jun 8 11:29:56 workstation kernel: [49956.666958] CPU: 8 PID: 706155 Comm: git Tainted: G IOE 5.11.0-18-generic #19-Ubuntu Jun 8 11:29:56 workstation kernel: [49956.666966] Hardware name: Dell Inc. Precision 5820 Tower X-Series/0X75JG, BIOS 2.2.0 04/14/2020 Jun 8 11:29:56 workstation kernel: [49956.666969] RIP: 0010:__kmalloc+0xb2/0x250 Jun 8 11:29:56 workstation kernel: [49956.666983] Code: 83 72 63 49 8b 00 49 83 78 10 00 48 89 45 c0 0f 84 85 01 00 00 48 85 c0 0f 84 7c 01 00 00 41 8b 4c 24 28 49 8b 3c 24 48 01 c1 <48> 8b 19 48 89 ce 49 33 9c 24 b8 00 00 00 48 8d 4a 01 48 0f ce 48 Jun 8 11:29:56 workstation kernel: [49956.666989] RSP: :ae48650b7878 EFLAGS: 00010282 Jun 8 11:29:56 workstation kernel: [49956.666996] RAX: e365a4770fa8aee0 RBX: RCX: e365a4770fa8af10 Jun 8 11:29:56 workstation kernel: [49956.667000] RDX: 00044185 RSI: 0d40 RDI: 000310c0 Jun 8 11:29:56 workstation kernel: [49956.667004] RBP: ae48650b78c0 R08: 9f9c9fa310c0 R09: 0001 Jun 8 11:29:56 workstation kernel: [49956.667008] R10: 0001 R11: R12: 9f8d40043a00 Jun 8 11:29:56 workstation kernel: [49956.667012] R13: 0060 R14: 9f8d40043a00 R15: 0d40 Jun 8 11:29:56 workstation kernel: [49956.667016] FS: 7f2038755f80() GS:9f9c9fa0() knlGS: Jun 8 11:29:56 workstation kernel: [49956.667021] CS: 0010 DS: ES: CR0: 80050033 Jun 8 11:29:56 workstation kernel: [49956.667024] CR2: 7f2038a1c000 CR3: 0002ac41e004 CR4: 003726e0 Jun 8 11:29:56 workstation kernel: [49956.667029] DR0: DR1: DR2: Jun 8 11:29:56 workstation kernel: [49956.667032] DR3: DR6: fffe0ff0 DR7: 0400 Jun 8 11:29:56 workstation kernel: [49956.667036] Call Trace: Jun 8 11:29:56 workstation kernel: [49956.667039] ? ext4_find_extent+0x381/0x450 Jun 8 11:29:56 workstation kernel: [49956.667051] ext4_find_extent+0x381/0x450 Jun 8 11:29:56 workstation kernel: [49956.667058] ext4_ext_map_blocks+0x72/0x980 Jun 8 11:29:56 workstation kernel: [49956.667064] ? find_get_entry+0xcd/0x160 Jun 8 11:29:56 workstation kernel: [49956.667073] ? find_get_entry+0xcd/0x160 Jun 8 11:29:56 workstation kernel: [49956.667080] ? ext4_es_lookup_extent+0x164/0x210 Jun 8 11:29:56 workstation kernel: [49956.667087] ext4_map_blocks+0x261/0x590 Jun 8 11:29:56 workstation kernel: [49956.667093] ? xas_load+0x9/0x80 Jun 8 11:29:56 workstation kernel: [49956.667103] ? xa_load+0x61/0x90 Jun 8 11:29:56 workstation kernel: [49956.667110] ext4_mpage_readpages+0x533/0xa70 Jun 8 11:29:56 workstation kernel: [49956.667118] ? __mod_lruvec_state+0x3a/0x50 Jun 8 11:29:56 workstation kernel: [49956.667127] ext4_readahead+0x33/0x40 Jun 8 11:29:56 workstation kernel: [49956.667132] read_pages+0x89/0x270 Jun 8 11:29:56 workstation kernel: [49956.667140] page_cache_ra_unbounded+0x137/0x1f0 Jun 8 11:29:56 workstation kernel: [49956.667147] do_page_cache_ra+0x3d/0x40 Jun 8 11:29:56 workstation kernel: [49956.667152] do_sync_mmap_readahead+0x10d/0x1c0 Jun 8 11:29:56 workstation kernel: [49956.667159] filemap_fault+0x571/0x840 Jun 8 11:29:56 workstation kernel: [49956.667166] ? xas_find+0x17a/0x1d0 Jun 8 11:29:56 workstation kernel: [49956.667172] ? filemap_map_pages+0x215/0x3f0 Jun 8 11:29:56 workstation kernel: [49956.667179] ext4_filemap_fault+0x32/0x50 Jun 8 11:29:56 workstation kernel: [49956.667185] __do_fault+0x3c/0xe0 Jun 8 11:29:56 workstation kernel: [49956.667194] do_fault+0xc4/0x1f0 Jun 8 11:29:56 workstation kernel: [49956.667201] handle_pte_fault+0x1e5/0x260 Jun 8 11:29:56 workstation kernel: [49956.667207] __handle_mm_fault+0x599/0x7c0 Jun 8 11:29:56 workstation kernel: [49956.667216] handle_mm_fault+0xd7/0x2b0 Jun 8 11:29:56 workstation kernel: [49956.667224] do_user_addr_fault+0x1a3/0x450 Jun 8 11:29:56 workstation kernel: [49956.667233] exc_page_fault+0x6c/0x150 Jun 8 11:29:56 workstation kernel: [49956.667242] ? asm_exc_page_fault+0x8/0x30 Jun 8 11:29:56 workstation kernel: [49956.667250] asm_exc_page_fault+0x1e/0x30 Jun 8 11:29:56 workstation kernel: [49956.667256] RIP: 0033:0x7f203897399c Jun 8 11:29:56 workstation kernel: [49956.667262] Code: 60 e9 e5 eb ff ff 0f 1f 84 00 00 00 00 00 8d 04 31 48 01 c7 e9 4a fa ff ff 83 fb 0f 0f 87 02 09 00 00 85 ed 0f 84 94 fb ff ff <41> 0f b6 55 00 89 d9 8d 75 ff 4d 8d 45 01 48 d3 e2 8d
[Kernel-packages] [Bug 1930976] Re: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
I can't tell which Nvidia driver, if any, is installed. Please run this command: dpkg -l > packages.txt and attach the resulting text file here. ** Changed in: linux-hwe-5.8 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930976 Title: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers Status in linux-hwe-5.8 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Kernel: 5.8.0-55 The last kernel destroyed my Ubuntu 20.04.02 installation, something went wrong with some kernel packages. It seems like Ubuntu is unable to find my video card correctly and the device drivers from Nvidia don't seem to work anymore. I had to do a clean installation, but even that doesn't solve the problem. I think this is a serious issue that needs to be looked into. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jun 5 16:50:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation Device [10de:2206] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:403f] InstallationDate: Installed on 2021-06-05 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=4984fe2f-d45f-4734-884c-2426bcf10ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33j dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33j:bd04/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1930976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930925] Re: Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but 18.04 does)
** Summary changed: - Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch + Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but 18.04 does) -- 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/1930925 Title: Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but 18.04 does) Status in linux package in Ubuntu: New Bug description: I have recently acquired a acquired a desktop running ubuntu 20.04. I have several computers and switch between them using this KVM https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 The other machines are either running windows or ubuntu 18.04 or earlier. They are all fine, but the with 20.04 machine neither the keyboard nor the mouse works. On the 18.04 machine I can see lsusb Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub and it is the Logitech, Inc. Unifying Receiver which appears when the USB from the KVM is connected. On the 20.04 machine only this appears lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I have tested installation discs from 19.04 onwards. The failure first appears in 19.10 and is still present in 21.04 I can observe a similar problem with a dual boot laptop running windows 10 and 20.04. With windows 10 I can use it with the KVM for screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and mouse do not work. This issue has also been observed here https://unix.stackexchange.com/questions/646515/using-logitech-mouse- keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model). I had to report this originally against xorg as this bug reporting system seems not to allow reporting of bugs against unknown packages. I also had to report it through the ubuntu-bug executable as I've been unable to find a way in launchpad of reporting a bug (as opposed to getting a guided tour about reporting bugs). I am happy to supply more info and test fixes if I am asked but as with this type of bug where something fails to happen rather than something wrong happens I don't know what to look at. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Jun 4 20:21:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-05-14 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 13: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 13: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=0c391c11-c570-4e04-a351-4fd128a75369 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2021 dmi.bios.release: 8.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0820 dmi.board.asset.tag: Default string dmi.board.name: PRIME H570M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.typ
[Kernel-packages] [Bug 1930794] Re: Ubuntu 20.04 LTS does not start after kernel update
*** This bug is a duplicate of bug 1930976 *** https://bugs.launchpad.net/bugs/1930976 ** This bug has been marked a duplicate of bug 1930976 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers -- 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/1930794 Title: Ubuntu 20.04 LTS does not start after kernel update Status in linux package in Ubuntu: New Bug description: Hi I got a notification to update my kernel to 5.8.0-55 and when I update and reboot my PC. The desktop does not start and when I downgrade my kernel 5.8.0-53. Again, it does not work either. Finally, I have to reimage my PC from the scratch and I lose all of my local data in this situation. I Hope you can solve this critical problem soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.4.0.1049.47)
All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1049.47) for focal have finished running. The following regressions have been reported in tests triggered by the package: iptables-netflow/2.4-2ubuntu0.4 (amd64) ddcci-driver-linux/0.3.3-1 (amd64) lttng-modules/2.12.2-1ubuntu1~20.04.2 (amd64) nvidia-graphics-drivers-460/460.80-0ubuntu0.20.04.2 (amd64) v4l2loopback/0.12.3-1ubuntu0.4 (amd64) west-chamber/20100405+svn2007.r124-12ubuntu0.3~20.04.1 (amd64) xtables-addons/3.9-1ubuntu0.2~20.04.1 (amd64) nat-rtsp/0.7+4.18-0.1ubuntu1 (amd64) broadcom-sta/6.30.223.271-12 (amd64) backport-iwlwifi-dkms/8324-0ubuntu3~20.04.3 (amd64) nvidia-graphics-drivers-450-server/450.119.04-0ubuntu0.20.04.2 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 (amd64) nvidia-graphics-drivers-460-server/460.73.01-0ubuntu0.20.04.1 (amd64) dm-writeboost/2.2.9-1ubuntu1.2 (amd64) gost-crypto/0.3.2-2ubuntu0.2 (amd64) nvidia-graphics-drivers-418-server/418.197.02-0ubuntu0.20.04.1 (amd64) sysdig/0.26.4-1ubuntu0.3 (amd64) snapd/2.49.2+20.04 (amd64) rtl8821ce/5.5.2.1-0ubuntu4~20.04.3 (amd64) bbswitch/0.8-8ubuntu0.20.04.1 (amd64) nvidia-graphics-drivers-390/390.143-0ubuntu0.20.04.1 (amd64) r8168/8.048.00-1ubuntu0.20.04.2 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 (amd64) openrazer/2.5.0+dfsg-1ubuntu2 (amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64) dpdk/19.11.7-0ubuntu0.20.04.1 (amd64) ndiswrapper/1.60-8ubuntu3 (amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (amd64) jool/4.0.7-1 (amd64) openafs/1.8.4~pre1-1ubuntu2.1 (amd64) adv-17v35x/5.0.3.0-2 (amd64) oss4/4.2-build2010-5ubuntu6~20.04.2 (amd64) tp-smapi/0.43-1 (amd64) lime-forensics/1.9-1ubuntu0.2 (amd64) virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.2 (amd64) acpi-call/1.1.0-5ubuntu0.2 (amd64) bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 (amd64) sl-modem/2.9.11~20110321-16ubuntu1 (amd64) langford/0.0.20130228-6build1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle/5.11.0.1008.8)
All autopkgtests for the newly accepted linux-meta-oracle (5.11.0.1008.8) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: systemd/247.3-3ubuntu3 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-oracle [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
Hi Khaled, I have finished testing the kernels - it took more time than I expected but the results are: 4.15.0-136-generic: no issues 4.15.0-137-generic: disk performance issue 4.15.0-139-generic: disk performance issue 4.15.0-140-generic: disk performance issue 4.15.0-142-generic: disk performance issue Each kernel was running for minimum 7 days. Those which have disk performance issue start to break after few days of normal workload. Here is an example of "iotop -a", when our disk operations are throttled: Actual DISK READ: 0.00 B/s | Actual DISK WRITE: 0.00 B/s TID PRIO USER DISK READ DISK WRITE SWAPIN IO>COMMAND 10908 be/4 barman0.00 B144.00 K 0.00 % 99.99 % pg_receivewal --dbname=dbname=replication host=XX replication=~o-password --directory=/data/barman/X/streaming --slot=barman 9494 be/4 barman0.00 B144.00 K 0.00 % 99.99 % rsync --server -logDtpre.iLsfxC . /data/barman/XX/incoming/0001318300ED 10907 be/4 barman0.00 B144.00 K 0.00 % 99.99 % pg_receivewal --dbname=dbname=replication host=XX replication~-password --directory=/data/barman/XXX/streaming --slot=barman 7148 be/4 barman0.00 B144.00 K 0.00 % 99.99 % rsync --server -logDtpre.iLsfxC . /data/barman/XX/incoming/0001D2E90043 11144 be/4 barman0.00 B144.00 K 0.00 % 99.99 % pg_receivewal --dbname=dbname=replication host=X replication=~o-password --directory=/data/barman/X/streaming --slot=barman 17724 be/3 root 0.00 B 8.00 K 0.00 % 99.99 % auditd 11217 be/4 root 0.00 B 8.00 K 0.00 % 99.99 % syslog-ng -F 10003 be/4 barman0.00 B 96.00 K 0.00 % 99.99 % gpg -e -r BarmanBackup 10219 be/4 barman0.00 B 96.00 K 0.00 % 99.99 % gpg -e -r BarmanBackup 9247 be/4 barman0.00 B140.00 K 0.00 % 98.62 % rsync --server -logDtpre.iLsfxC . /data/barman/mel-attn-hostdb/incoming/00014CE00083 11391 be/4 barman0.00 B140.00 K 0.00 % 98.60 % pg_receivewal --dbname=dbname=replication host=XXX replication=~o-password --directory=/data/barmanXXX/streaming --slot=barman 9556 be/4 barman0.00 B 92.00 K 0.00 % 98.53 % gpg -e -r BarmanBackup 4381 be/4 root 0.00 B 8.00 K 0.00 % 57.53 % sadc -F -L -S DISK 60 /var/log/sysstat 10959 be/4 root 0.00 B 4.00 K 0.00 % 26.29 % sadc -F -L -S DISK 60 /var/log/sysstat 15626 be/4 root 0.00 B 4.00 K 0.00 % 8.22 % sadc -F -L -S DISK 60 /var/log/sysstat So, I think it is ok to say that the problem was introduced with 4.15.0-137-generic. We will try to see the latest kernel in our next patching window. However, based on the fact that kernels 137,139,140,142 are not working correctly, could this be related to some tuning changes? In our case, we haven't done any changes to e.g. sysctl after patching. Many thanks for your help so far! -- 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/1928744 Title: Disk IO very slow on kernel 4.15.0-142-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: After upgrading Ubuntu 18.04 kernel from 4.15.0-136-generic to kernel 4.15.0-142-generic disk IOs (writes) are suffering from terrible delay. Time required to write 1GB of data to the dist is ~12 minutes. 1GB in 12 minutes: strace -ttvvff -o mel.strace dd bs=1024k count=1024 if=/dev/zero of=/data/disk_test/dd_test Before the upgrade, it took seconds to complete. The only change which was done on the system was security upgrade done with unattended-upgrade utility and main repositories for bionic and bionic-security. This is physical server LENOVO System x3650 M5, with Symbios Logic MegaRAID SAS-3 3108 disk controller. The only difference which I see is that there are more modules loaded by the latest kernel. I would expect that the performance would be the same. There were no changes to the physical server and the disks are reported as online and healthy. No only dd is affected but also all disk-based operation by barman (we are using postgres steaming backup along with rsync/ssh archiving). I think this could be a kernel bug. I would be happy to provide other information which would help in fixing this problem. = Details: lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 lsmod Module Size Used by ip6_tables 28672 0 iptable_filter 16384 0 ip_tables 28672 1 iptable_filter x_tables 40960 3 iptabl
[Kernel-packages] [Bug 1930976] Re: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930976 Title: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers Status in linux-hwe-5.8 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: Kernel: 5.8.0-55 The last kernel destroyed my Ubuntu 20.04.02 installation, something went wrong with some kernel packages. It seems like Ubuntu is unable to find my video card correctly and the device drivers from Nvidia don't seem to work anymore. I had to do a clean installation, but even that doesn't solve the problem. I think this is a serious issue that needs to be looked into. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jun 5 16:50:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation Device [10de:2206] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:403f] InstallationDate: Installed on 2021-06-05 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=4984fe2f-d45f-4734-884c-2426bcf10ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33j dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33j:bd04/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1930976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930976] Re: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe-5.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930976 Title: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers Status in linux-hwe-5.8 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: Kernel: 5.8.0-55 The last kernel destroyed my Ubuntu 20.04.02 installation, something went wrong with some kernel packages. It seems like Ubuntu is unable to find my video card correctly and the device drivers from Nvidia don't seem to work anymore. I had to do a clean installation, but even that doesn't solve the problem. I think this is a serious issue that needs to be looked into. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jun 5 16:50:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation Device [10de:2206] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:403f] InstallationDate: Installed on 2021-06-05 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=4984fe2f-d45f-4734-884c-2426bcf10ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33j dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33j:bd04/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1930976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931292] Re: Hirsute update: v5.11.22 upstream stable release
** 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, 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:
- 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.11.22 upstream stable release
+ from git://git.kernel.org/
-v5.11.22 upstream stable release
-from git://git.kernel.org/
+ KEYS: trusted: Fix memory leak on object td
+ tpm: fix error return code in tpm2_get_cc_attrs_tbl()
+ tpm, tpm_tis: Extend locality handling to TPM2 in tpm_tis_gen_interrupt()
+ tpm, tpm_tis: Reserve locality in tpm_tis_resume()
+ KVM: SVM: Make sure GHCB is mapped before updating
+ KVM: x86/mmu: Remove the defunct update_pte() paging hook
+ KVM/VMX: Invoke NMI non-IST entry instead of IST entry
+ ACPI: PM: Add ACPI ID of Alder Lake Fan
+ PM: runtime: Fix unpaired parent child_count for force_resume
+ cpufreq: intel_pstate: Use HWP if enabled by platform firmware
+ kvm: Cap halt polling at kvm->max_halt_poll_ns
+ ath11k: fix thermal temperature read
+ ALSA: usb-audio: Add Pioneer DJM-850 to quirks-table
+ fs: dlm: fix debugfs dump
+ fs: dlm: fix mark setting deadlock
+ fs: dlm: add errno handling to check callback
+ fs: dlm: add check if dlm is currently running
+ fs: dlm: change allocation limits
+ fs: dlm: check on minimum msglen size
+ fs: dlm: flush swork on shutdown
+ fs: dlm: add shutdown hook
+ tipc: convert dest node's address to network order
+ ASoC: Intel: bytcr_rt5640: Enable jack-detect support on Asus T100TAF
+ net/mlx5e: Use net_prefetchw instead of prefetchw in MPWQE TX datapath
+ net: stmmac: Set FIFO sizes for ipq806x
+ ASoC: rsnd: core: Check convert rate in rsnd_hw_params
+ Bluetooth: Fix incorrect status handling in LE PHY UPDATE event
+ i2c: bail out early when RDWR parameters are wrong
+ ALSA: hdsp: don't disable if not enabled
+ ALSA: hdspm: don't disable if not enabled
+ ALSA: rme9652: don't disable if not enabled
+ ALSA: bebob: enable to deliver MIDI messages for multiple ports
+ Bluetooth: Set CONF_NOT_COMPLETE as l2cap_chan default
+ Bluetooth: initialize skb_queue_head at l2cap_chan_create()
+ net/sched: cls_flower: use ntohs for struct flow_dissector_key_ports
+ net: bridge: when suppression is enabled exclude RARP packets
+ Bluetooth: check for zapped sk before connecting
+ selftests/powerpc: Fix L1D flushing tests for Power10
+ powerpc/32: Statically initialise first emergency context
+ net: hns3: remediate a potential overflow risk of bd_num_list
+ net: hns3: add handling for xmit skb with recursive fraglist
+ ip6_vti: proper dev_{hold|put} in ndo_[un]init methods
+ ASoC: Intel: bytcr_rt5640: Add quirk for the Chuwi Hi8 tablet
+ ice: handle increasing Tx or Rx ring sizes
+ Bluetooth: btusb: Enable quirk boolean flag for Mediatek Chip.
+ ASoC: rt5670: Add a quirk for the Dell Venue 10 Pro 5055
+ selftests: mptcp: launch mptcp_connect with timeout
+ i2c: Add I2C_AQ_NO_REP_START adapter quirk
+ Bluetooth: Do not set cur_adv_instance in adv param MGMT request
+ MIPS: Loongson64: Use _CACHE_UNCACHED instead of _CACHE_UNCACHED_ACCELERATED
+ coresight: Do not scan for graph if none is present
+ IB/hfi1: Correct oversized ring allocation
+ mac80211: Set priority and queue mapping for injected frames
+ mac80211: clear the beacon's CRC after channel switch
+ ASoC: soc-compress: lock pcm_mutex to resolve lockdep error
+ pinctrl: samsung: use 'int' for register masks in Exynos
+ rtw88: 8822c: add LC calibration for RTL8822C
+ mt76: mt7615: fix key set/delete issues
+ mt76: mt7615: support loading EEPROM for MT7613BE
+ mt76: mt76x0: disable GTK offloading
+ mt76: mt7915: always check return value from mt7915_mcu_alloc_wtbl_req
+ mt76: mt7915: fix key set/delete issue
+ mt76: mt7915: fix txpower init for TSSI off chips
+ mt76: mt7915: add wifi subsystem reset
+ i2c: imx: Fix PM reference leak in i2c_imx_reg_slave()
+ fuse: invalidate attrs when page writeback completes
+ virtiofs: fix userns
+ cuse: prevent clone
+ iwlwifi: pcie: make cfg vs. trans_cfg more robust
+ iwlwifi: queue: avoid memory leak in reset flow
+ powerpc/mm: Add cond_resched() while removing hpte mappings
+ ASoC: rsnd: call rsnd_ssi_master_clk_start() from rsnd_ssi_init()
+ Revert "iommu/amd: Fix performance counter initial
[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
Why not downgrade 460 & 465 in the repo? Its causing issues with new install. I have a friend who suffered that same problem, and I have to walk her through GRUB in order to install the server driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-465 package in Ubuntu: Triaged Bug description: I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute Jun 03 16:26:57 willow kernel: Oops: [#1] SMP PTI Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P OE 5.11.0-18-generic #19-Ubuntu Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019 Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 R09: 8e318220acb8 Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 R12: 0400 Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 R15: 0800 Jun 03 16:26:57 willow kernel: FS: 7f5807f38a40() GS:8e3466dc() knlGS: Jun 03 16:26:57 willow kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 CR4: 003706e0 Jun 03 16:26:57 willow kernel: DR0: DR1: DR2: Jun 03 16:26:57 willow kernel: DR3: DR6: fffe0ff0 DR7: 0400 Jun 03 16:26:57 willow kernel: Call Trace: Jun 03 16:26:57 willow kernel: ? _nv015556rm+0x7fd/0x1020 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv027155rm+0x22c/0x4f0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017787rm+0x303/0x5e0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017789rm+0xe1/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv022829rm+0xed/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv023065rm+0x30/0x60 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv000704rm+0x16da/0x22b0 [nvidia] Jun 03 16:26:57 willow kernel: ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 03 16:26:57 willow kernel: ? nv_open_device+0x122/0x8e0 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_open+0x2b7/0x560 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 03 16:26:57 willow kernel: ? chrdev_open+0xf7/0x220 Jun 03 16:26:57 willow kernel: ? cdev_device_add+0x90/0x90 Jun 03 16:26:57 willow kernel: ? do_dentry_open+0x156/0x370 Jun 03 16:26:57 willow kernel: ? vfs_open+0x2d/0x30 Jun 03 16:26:57 willow kernel: ? do_open+0x1c3/0x340 Jun 03 16:26:57 willow kernel: ? path_openat+0x10a/0x1d0 Jun 03 16:26:57 willow kernel: ? do_filp_open+0x8c/0x130 Jun 03 16:26:57 willow kernel: ? __check_object_size+0x1c/0x20 Jun 03 16:26:57 willow kernel: ? do_sys_openat2+0x9b/0x150 Jun 03 16:26:57 willow kernel: ? __x64_sys_openat+0x56/0x90 Jun 03 16:26:57 willow kernel: ? do_syscall_64+0x38/0x90 Jun 03 16:26:57 willow kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) > Jun 03 16:26:57 willow kernel: sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c> Jun 03 16:26:57 willow kernel: CR2: 0170 Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]--- Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0
[Kernel-packages] [Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
I've checked provided kernel and seems nothing has changed. Keys still does't work and dmesg is sielent when I'm pressing mic mute. For Fn+F10 it seems that the closest behavior would be to take selective screenshot. But if there is no such event defined that it might be mapped as a generic Fn button so it still could be used. -- 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/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I found that some of the Lenovo Lenovo Essential Wireless Keyboard Fn keys don't work. First one is Mute mic (Fn+F4), second one is Scissors (Fn+F10, probably hotkey for Windows Snipping Tool for selective screenshot).gnome-control-panel, xev and evtest doesn't react on pressing these buttons. Here what I was able to get via sudo cat /dev/usb/hiddev0 | hexdump -v -e '/1 "%02X\n"' : For Mute key 00 00 00 FF DC 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 For Scissors 00 00 00 FF DB 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asudak 2085 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 6 22:36:50 2021 InstallationDate: Installed on 2021-04-13 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-18 (17 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp/5.4.0.1044.54)
All autopkgtests for the newly accepted linux-meta-gcp (5.4.0.1044.54) for focal have finished running. The following regressions have been reported in tests triggered by the package: adv-17v35x/5.0.3.0-2 (amd64) lime-forensics/1.9-1ubuntu0.2 (amd64) iptables-netflow/2.4-2ubuntu0.4 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 (amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64) v4l2loopback/0.12.3-1ubuntu0.4 (amd64) acpi-call/1.1.0-5ubuntu0.2 (amd64) nat-rtsp/0.7+4.18-0.1ubuntu1 (amd64) nvidia-graphics-drivers-460/460.80-0ubuntu0.20.04.2 (amd64) xtables-addons/3.9-1ubuntu0.2~20.04.1 (amd64) nvidia-graphics-drivers-418-server/418.197.02-0ubuntu0.20.04.1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 (amd64) r8168/8.048.00-1ubuntu0.20.04.2 (amd64) sl-modem/2.9.11~20110321-16ubuntu1 (amd64) dm-writeboost/2.2.9-1ubuntu1.2 (amd64) langford/0.0.20130228-6build1 (amd64) openafs/1.8.4~pre1-1ubuntu2.1 (amd64) nvidia-graphics-drivers-390/390.143-0ubuntu0.20.04.1 (amd64) rtl8821ce/5.5.2.1-0ubuntu4~20.04.3 (amd64) backport-iwlwifi-dkms/8324-0ubuntu3~20.04.3 (amd64) openrazer/2.5.0+dfsg-1ubuntu2 (amd64) ddcci-driver-linux/0.3.3-1 (amd64) jool/4.0.7-1 (amd64) lttng-modules/2.12.2-1ubuntu1~20.04.2 (amd64) nvidia-graphics-drivers-460-server/460.73.01-0ubuntu0.20.04.1 (amd64) oss4/4.2-build2010-5ubuntu6~20.04.2 (amd64) west-chamber/20100405+svn2007.r124-12ubuntu0.3~20.04.1 (amd64) tp-smapi/0.43-1 (amd64) virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.2 (amd64) ndiswrapper/1.60-8ubuntu3 (amd64) sysdig/0.26.4-1ubuntu0.3 (amd64) bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 (amd64) broadcom-sta/6.30.223.271-12 (amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (amd64) nvidia-graphics-drivers-450-server/450.119.04-0ubuntu0.20.04.2 (amd64) gost-crypto/0.3.2-2ubuntu0.2 (amd64) bbswitch/0.8-8ubuntu0.20.04.1 (amd64) dpdk/19.11.7-0ubuntu0.20.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-gcp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1598 https://gitlab.freedesktop.org/drm/amd/-/issues/1598 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #920 https://gitlab.freedesktop.org/drm/amd/-/issues/920 -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: New Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Thanks for your input. Em terça-feira, 8 de junho de 2021, às 10:30:24 -03, Alex Deucher escreveu: > Can you narrow down which specific firmware file causes the problem? Ok, I will try. Also, is it possible and/or worthwhile trying to bisect firmware versions from the linux-firmware repo? How coupled is the firmware with the kernel driver? E.g., can I try using firmware files from 1 year ago with current kernel and Mesa? > We haven't been able to repro this. One thing that’s a bit “fishy” about my machine is that it doesn’t seem to have a good clock: [0.211436] TSC synchronization [CPU#0 -> CPU#1]: [0.211436] Measured 3304683447 cycles TSC warp between CPUs, turning off TSC clock. [0.211436] tsc: Marking TSC unstable due to check_tsc_sync_source failed … [0.252117] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0 [0.252117] hpet0: 3 comparators, 32-bit 14.318180 MHz counter [0.253970] clocksource: Switched to clocksource hpet … [0.580451] Unstable clock detected, switching default tracing clock to "global" If you want to keep using the local clock, then add: "trace_clock=local" on the kernel command line Could this bug be related to that? > I think it may be related to a change in mesa. Specifically mesa commit > 820dec3f7c7. For more info see > https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 I’ll run with Mario’s build of Mesa with that patch backported. Thanks, Mario! > ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #4866 >https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 Other upstream issues that look similar: https://gitlab.freedesktop.org/drm/amd/-/issues/1598 https://gitlab.freedesktop.org/drm/amd/-/issues/920 -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: New Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931105] Re: Sleep issue on ubuntu 21.04, CPU AMD 5700u
** Tags added: kernel-bug suspend-resume -- 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/1931105 Title: Sleep issue on ubuntu 21.04, CPU AMD 5700u Status in linux package in Ubuntu: New Bug description: System Info Dell Inspiron 5515 Operating System: Kubuntu 21.04 Kernel Version: 5.12.9-051209-generic OS Type: 64-bit Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics Memory: 15,1 GiB of RAM Graphics Processor: AMD RENOIR If I suspend my pc, the screen, fans and keyboard backlight turn off. However if I try to wake up from suspension the screen stays black, while the keyboard backlight starts blinking. The only way to unlock it is to click the power button, and the pc will automatically restart (thus losing the data of the active session). Initially I had the 5.11 kernel, then to see if the problem was solved I tried to install the 5.12 kernel and the 5.12.9 kernel, but there were no improvements. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931292] [NEW] Hirsute update: v5.11.22 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.11.22 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Hirsute) Importance: Medium 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 Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** 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/1931292 Title: Hirsute update: v5.11.22 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: In Progress Bug description: 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.11.22 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930921] Re: Apache 2.4.41 corrupts files from samba share
** Changed in: apache2 (Ubuntu) Status: New => Confirmed ** Changed in: samba (Ubuntu) Status: New => Confirmed ** 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/1930921 Title: Apache 2.4.41 corrupts files from samba share Status in apache2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Bug description: Wenn I serve a samba share with apache 2.4.41 on Ubuntu 20.04 then some files have a corrupt header during transmission. It seems that the first few bytes of the headers are truncated and sometimes other bytes of the download are not belonging to the file. A workaround I found that works is to set "EnableMMAP Off" in the apache config. See other bug reports like this: https://serverfault.com/questions/1044724/apache2-sends-corrupt-responses-when-using-a-cifs-share https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900821 This is most probably not a bug in Ubuntu itself but I am reporting it here since I assume that a data corruption bug is seen as critical. I am also marking it as a security vulnerability since it seems that wrong parts of memory get exposed during file download. I don't know how random the exposed memory is and if it potentially could expose e.g. secrets. Please feel free to remove the security vulnerability flag if your assessment leads to a different conclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1930921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927866] Re: Root filesystem becomes readonly frequenty freezing system
I tried to re-create the scenario that causes it to crash but have been unsuccessful so far. It crashed a few minutes back. Even now I am not too sure what exactly causes it to crash. So far what I have seen is that (i.e. after the re-install) the crashes have happened after I resume the system from sleep / suspend and login and start doing something. Still not been able to replicate this exactly though. I wish there was some way we could capture more logging. Keep a USB drive mounted and use that for /var/log? I am going to go ahead and install the updated kernel now. -- 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/1927866 Title: Root filesystem becomes readonly frequenty freezing system Status in linux package in Ubuntu: Confirmed Bug description: I have a brand new Lenovo Ideapad Flex 5.14 which came with Windows 10 and I have installed Ubuntu 21.04 with dual boot. I am running into this problem where the root filesystem becomes readonly and the system freezes with a screen full of errors shown about unable to write to filesystem. I booted into a live boot usb and did fsck and e2fsck but did not see any errors there. I read online that this could be because of io errors but smartctl and fsck does not show any errors So I was wondering if this could be a bug vs a hardward issue. Please let me know if you need any further information from the system. = = fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: WDC PC SN530 SDBPMPZ-512G-1101 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E8803E28-C4F7-4FA5-9B6D-0F3CAB7027A5 Device StartEnd Sectors Size Type /dev/nvme0n1p1 2048 534527532480 260M EFI System /dev/nvme0n1p2534528 567295 3276816M Microsoft reserved /dev/nvme0n1p3567296 199446527 198879232 94.8G Microsoft basic data /dev/nvme0n1p4 998166528 1000214527 2048000 1000M Windows recovery environmen /dev/nvme0n1p5 199446528 203352063 3905536 1.9G Linux filesystem /dev/nvme0n1p6 203352064 219353087 16001024 7.6G Linux swap /dev/nvme0n1p7 219353088 414664703 195311616 93.1G Linux filesystem /dev/nvme0n1p8 414664704 998166527 583501824 278.2G Microsoft basic data = = smartctl -a /dev/nvme0 smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.0-16-generic] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: WDC PC SN530 SDBPMPZ-512G-1101 Serial Number: 205135806243 Firmware Version: 21160001 PCI Vendor/Subsystem ID:0x15b7 IEEE OUI Identifier:0x001b44 Total NVM Capacity: 512,110,190,592 [512 GB] Unallocated NVM Capacity: 0 Controller ID: 1 NVMe Version: 1.4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 512,110,190,592 [512 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64:001b44 8b484daff7 Local Time is: Sun May 9 12:45:05 2021 EDT Firmware Updates (0x14):2 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg Maximum Data Transfer Size: 128 Pages Warning Comp. Temp. Threshold: 80 Celsius Critical Comp. Temp. Threshold: 85 Celsius Namespace 1 Features (0x02):NA_Fields Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 3.50W2.10W -0 0 0 00 0 1 + 2.40W1.60W -0 0 0 00 0 2 + 1.90W1.50W -0 0 0 00 0 3 - 0.0250W --3 3 3 3 3900 11000 4 - 0.0050W --4 4 4 4 5000 39000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 2 1 -4096 0 1 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature:3
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gke-5.4/5.4.0.1045.47~18.04.11)
All autopkgtests for the newly accepted linux-meta-gke-5.4 (5.4.0.1045.47~18.04.11) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (amd64) virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) zfs-linux/0.7.5-1ubuntu16.11 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gke-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
OK, so we know two things now: 1) The issue happens when the CPU reaches deeper power saving state, likely PC10. 2) Temporarily increase CPU usage via cpu_latency_qos_add_request() to disable C-State doesn't help. So please file an upstream bug at https://bugzilla.kernel.org/ Product: Drivers Component: Network -- 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/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got a Thinkpad T14 Gen2 with a I219-V network adapter (8086:15fc). I get very slow connection speeds and even total loss of connectivity without seeing much in the logs (like dmesg etc.). ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel 5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried the e1000e driver directly from upstream (3.8.7) with no success. A strange behaviour I observed: if connectivity is lost (notebook is not reachable via ping from another host), if I do something like "ping 8.8.8.8" on the notebook itself, it becomes reachable from the other host again. Downloads in general are very slow if they work at all. WLAN (AX210) seems to work fine, wired network using a USB-network adapter works fine, too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros3285 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-05-07 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20W0004MGE NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0004MGE dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1673 F pulseaudio /dev/snd/controlC1: ros1673 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20W0004MGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1026-oem N/A linux-backports-modules-5.10.0-1026-oem N/A linux-firmware 1.187.12 Tags: focal Uname: Linux 5.10.0-1026-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information
[Kernel-packages] [Bug 1925843] Re: Linux 5.8.0-49+ fails to resume from suspend
Yes, you should use good/bad in reverse. -- 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/1925843 Title: Linux 5.8.0-49+ fails to resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Expected Result: System resumes from suspend and displays the log in screen to unlock the computer. Actual Result: System displays a black screen with a flashing cursor in the upper left and cannot be interacted with. Hard reboot is required to get back to a working system. Additional information: When I boot my computer with 5.8.0-48, the system resumes from suspend as expected. Both 5.8.0-49 and 5.8.0-50 fail to resume from suspend. This problem began after I updated from 20.04 to 20.10 using the Software Updater on 4-19-21. I was using the latest kernel available for 20.04 at that time (5.8.0-48, I think) before updating. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-50-generic 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 1268 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 12:54:52 2021 InstallationDate: Installed on 2020-09-01 (234 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:58eb Realtek Semiconductor Corp. HP Wide Vision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 15-ce0xx 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.8.0-50-generic root=UUID=208c1c0d-3e9e-43da-ba24-0d1cd92b5ad0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 15.23 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 838F dmi.board.vendor: HP dmi.board.version: 40.28 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.28 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.23:bd10/30/2020:br15.23:efr40.28:svnHP:pnOMENbyHPLaptop15-ce0xx:pvr:rvnHP:rn838F:rvr40.28:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-ce0xx dmi.product.sku: 1KV78UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931251] Re: package nvidia-kernel-common-390 390.143-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-kernel-common-390 package post-installation script subprocess
** Tags removed: need-duplicate-check -- 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/1931251 Title: package nvidia-kernel-common-390 390.143-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-kernel-common-390 package post- installation script subprocess returned error exit status 1 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: While installing Ubuntu on my machine I received an error and I was prompted to send a crash - failure report. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-common-390 390.143-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 8 12:34:49 2021 Dependencies: ErrorMessage: installed nvidia-kernel-common-390 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-kernel-common-390 390.143-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-kernel-common-390 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1931251/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931251] Re: package nvidia-kernel-common-390 390.143-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-kernel-common-390 package post-installation script subprocess
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1931251 Title: package nvidia-kernel-common-390 390.143-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-kernel-common-390 package post- installation script subprocess returned error exit status 1 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: While installing Ubuntu on my machine I received an error and I was prompted to send a crash - failure report. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-common-390 390.143-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 8 12:34:49 2021 Dependencies: ErrorMessage: installed nvidia-kernel-common-390 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-kernel-common-390 390.143-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-kernel-common-390 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1931251/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.8.0.1029.31)
All autopkgtests for the newly accepted linux-meta-kvm (5.8.0.1029.31) for groovy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-450-server/450.119.04-0ubuntu0.20.10.2 (amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.10.2 (amd64) nvidia-graphics-drivers-418-server/418.197.02-0ubuntu0.20.10.1 (amd64) nvidia-graphics-drivers-390/390.143-0ubuntu0.20.10.1 (amd64) nvidia-graphics-drivers-460-server/460.73.01-0ubuntu0.20.10.1 (amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.10.1 (amd64) nvidia-graphics-drivers-460/460.80-0ubuntu0.20.10.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.11.0.1009.9)
All autopkgtests for the newly accepted linux-meta-kvm (5.11.0.1009.9) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: systemd/247.3-3ubuntu3 (amd64) rtl8821ce/5.5.2.1-0ubuntu6 (amd64) oss4/4.2-build2010-5ubuntu8 (amd64) sl-modem/2.9.11~20110321-16ubuntu1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64) v4l2loopback/0.12.5-1ubuntu1 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu14 (amd64) backport-iwlwifi-dkms/8613-0ubuntu2 (amd64) virtualbox/6.1.18-dfsg-5 (amd64) lttng-modules/2.12.2-1ubuntu3 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931106] Re: bnxt_en NIC driver crashes IO_PAGE_FAULT
Can you please raise the issue to the following mail address: $ scripts/get_maintainer.pl -f drivers/net/ethernet/broadcom/bnxt Michael Chan (supporter:BROADCOM BNXT_EN 50 GIGABIT ETHERNET DRIVER) "David S. Miller" (maintainer:NETWORKING DRIVERS) Jakub Kicinski (maintainer:NETWORKING DRIVERS) net...@vger.kernel.org (open list:BROADCOM BNXT_EN 50 GIGABIT ETHERNET 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/1931106 Title: bnxt_en NIC driver crashes IO_PAGE_FAULT Status in linux package in Ubuntu: Incomplete Bug description: Hi all, We received a bunch of new servers with a Supermicro H12SSL-NT mainboard that has an embedded Broadcom BCM57416 NIC. On all those servers we observe crashes of the NIC driver (bnxt_en) from time to time. We're not able to manually reproduce this issue, it just occurs at some point. Also our monitoring does not show any irregularities(high traffic flow or sth. like this). Syslog: https://pastebin.com/yDAyjHvF All servers are running with up-to-date packages: $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 $ uname -r 5.4.0-73-generic It also happens on older kernel versions (tested 5.4.0-66) as well as the HWE kernel (tested 5.8.0-55). Thanks in advance. ~ Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
So I tried to recreate and provoke any problems with the IP addresses on a test LPAR that has in between 5 OSA based qeth devices (4 of them with two addresses - one on base, one on the vlan device) and 4 RoCE (v1) ports. Other than finding out that one of the RoCE ports has probably no link (which is a different issue) everything worked fine so far. And the journal log you provided (thx for that) only shows that the enP53p0s0.171 is not activated (at least for ipv6) after the second systemd network-service start: ... Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd[1]: Starting Network Service... Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: encdb0.160: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: encdc0.150: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: enP50s3832.170: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: enP53p0s0.171: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: enP53p0s0: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: enP50s3832: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: ence0f: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: encdc0: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: encdb0: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: Enumeration completed Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd[1]: Started Network Service. Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: encdb0.160: IPv6 successfully enabled Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: encdc0.150: IPv6 successfully enabled Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: enP50s3832.170: IPv6 successfully enabled Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: enP53p0s0: IPv6 successfully enabled Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: enP50s3832: IPv6 successfully enabled Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: ence0f: IPv6 successfully enabled Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: encdc0: IPv6 successfully enabled Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: encdb0: IPv6 successfully enabled ... On the first the seems to be some activity. Unfortunately there are not enough details (in the regular journal log) to dig deeper into this - the above snippet is largely it. Would it be possible to enable verbose journaling 'journalctl -o verbose' hoping that we are then able to find more details - not sure what it will bring on top (or if this is not sufficient maybe even running systemd in debug mode). -- 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/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:
[Kernel-packages] [Bug 1931254] Re: Google Confidential Compute fails to boot with 1.47
Per the last comment, if the kernel is panicking, we should look at this from the kernel side. ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- 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/1931254 Title: Google Confidential Compute fails to boot with 1.47 Status in linux-gcp package in Ubuntu: New Status in shim-signed package in Ubuntu: New Bug description: # Overview Hirsute and Impish daily builds are currently not booting on Google Confidential Compute. Confidential compute is Google's platform that enables the use of Secure Encrypted Virtualization extension via AMD EPYC CPUs. Booting an image with version 1.45 works, but once upgraded to 1.47, the VM no longer boots, and instead the kernel panics. Launching the image with secure boot, but without confidential compute works as expected. # Expected result The system is able to reboot after the upgrade. # Actual result Kernel panic: https://paste.ubuntu.com/p/mHrvVc6qBc/ # Steps to reproduce Launch a VM in GCE with confidential compute enabled with a serial v20210511a or later and look at the serial log for the kernel panic. Example CLI command to launch a VM: $ gcloud beta compute instances create $USER-confidential-testing --zone=us-west1-b --machine-type=n2d-standard-2 --image=daily- ubuntu-2104-hirsute-v20210511a --image-project=ubuntu-os-cloud-devel --confidential-compute --maintenance-policy=TERMINATE The last known good working image is daily- ubuntu-2104-hirsute-v20210510. The upgrade that fails is when shim signed is updated from 1.46+15.4-0ubuntu1 to 1.47+15.4-0ubuntu2 # Logs & notes * 20210510 manifest (good): https://paste.ubuntu.com/p/QjnMPcJj7G/ * 20210511a manifest (bad): https://paste.ubuntu.com/p/PvJQwRXHcG/ * diff between manifests: https://paste.ubuntu.com/p/4nJtGxqGn7/ * serial logs of failed boot: https://paste.ubuntu.com/p/mHrvVc6qBc/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1931254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
Thanks Matt. I have it installed on one machine so far and looks good (in the past 10 minutes). fstrim of a ~30 TB RAID 10 took 73 seconds instead of multiple hours. # uname -a Linux xxx 5.4.0-75-generic #84-Ubuntu SMP Fri May 28 16:28:37 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux # df -h /dev/md0 Filesystem Size Used Avail Use% Mounted on /dev/md0 30T 212G 29T 1% /opt/raid # cat /proc/mdstat Personalities : [raid10] [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] md0 : active raid10 nvme7n1[7] nvme2n1[2] nvme6n1[6] nvme4n1[4] nvme1n1[1] nvme3n1[3] nvme0n1[0] nvme5n1[5] 31255576576 blocks super 1.2 512K chunks 2 near-copies [8/8] [] bitmap: 11/233 pages [44KB], 65536KB chunk unused devices: # time fstrim /opt/raid real1m13.162s user0m0.004s sys 0m0.351s -- 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/1896578 Title: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. These commits have now landed in 5.13-rc1. commit cf78408f937a67f59f5e90ee8e6cadeed7c128a8 Author: Xiao Ni Date: Thu Feb 4 15:50:43 2021 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://github.com/torvalds/linux/commit/cf78408f937a67f59f5e90ee8e6cadeed7c128a8 commit c2968285925adb97b9aa4ede94c1f1ab61ce0925 Author: Xiao Ni Date: Thu Feb 4 15:50:44 2021 +0800 Subject: md/raid10: extend r10bio devs to raid disks Link: https://github.com/torvalds/linux/commit/c2968285925adb97b9aa4ede94c1f1ab61ce0925 commit f2e7e269a7525317752d472bb48a549780e87d22 Author: Xiao Ni Date: Thu Feb 4 15:50:45 2021 +0800 Subject: md/raid10: pull the code that wait for blocked dev into one function Link: https://github.com/torvalds/linux/commit/f2e7e269a7525317752d472bb48a549780e87d22 commit d30588b2731fb01e1616cf16c3fe79a1443e29aa Author: Xiao Ni Date: Thu Feb 4 15:50:46 2021 +0800 Subject: md/raid10: improve raid10 discard request Link: https://github.com/torvalds/linux/commit/d30588b2731fb01e1616cf16c3fe79a1443e29aa commit 254c271da0712ea8914f187588e0f81f7678ee2f Author: Xiao Ni Date: Thu Feb 4 15:50:47 2021 +0800 Subject: md/raid10: improve discard request for far layout Link: https://github.com/torvalds/linux/commit/254c271da0712ea8914f187588e0f81f7678ee2f There is also an additional commit which is required, and was merged
[Kernel-packages] [Bug 1909814] Re: Keyboard not working
@replydev: Can you tell us, what machine you are using? E.g. with "dmesg | grep DMI:" Just for completeness of infos. TIA -- 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/1909814 Title: Keyboard not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Here's a PPA build with the mesa fix Alex mentioned backported: https://launchpad.net/~superm1/+archive/ubuntu/lp1928393 If you can follow the directions to add that PPA and upgrade to that mesa package you can see if that indeed fixes it. ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: New Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836167] Re: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes
The offline error: "sh: echo: I/O error cpuhotplug03 1 TBROK: CPU1 cannot be offlined" seems to be reproducible only on Azure, not on AWS. If AWS was affected by this bug, it could be different issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836167 Title: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: <<>> incrementing stop Name: cpuhotplug03 Date: Thu Jul 11 08:31:48 UTC 2019 Desc: Do tasks get scheduled to a newly on-lined CPU? CPU is 1 sh: echo: I/O error cpuhotplug03 1 TBROK: CPU1 cannot be offlined USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 4642 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4643 0.0 0.0 2020 480 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4644 0.0 0.0 2020 468 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4645 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4646 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4647 0.0 0.0 2020 480 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4648 0.0 0.0 2020 456 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4649 0.0 0.0 2020 508 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4650 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4651 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4652 0.0 0.0 2020 484 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4653 0.0 0.0 2020 496 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4654 0.0 0.0 2020 464 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4655 0.0 0.0 2020 492 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4656 0.0 0.0 2020 448 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4657 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4661 0.0 0.0 7540 648 pts/0S08:31 0:00 grep cpuhotplug_do_spin_loop cpuhotplug03 1 TINFO: Onlining CPU 1 7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop cpuhotplug03 1 TPASS: 2 cpuhotplug_do_spin_loop processes found onCPU1 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=2 corefile=no cutime=1060 cstime=9 <<>> Test passed on ThunderX ARM64, probably a test case issue. Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "cpuhotplug03 cpuhotplug03.sh -c 1 -l 1" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-25-generic 4.18.0-25.26 ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20 Uname: Linux 4.18.0-25-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 11 06:57 seq crw-rw 1 root audio 116, 33 Jul 11 06:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.4 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or
[Kernel-packages] [Bug 1931245] Re: driver/broadcom/bnxt: invalid dev_port
Sent backport for v5.4 stable. Greg replied, that backport is queued for
v4.9, v4.14, v4.19 and v5.4, so Focal will get it via regular stable
update
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Invalid
** Changed in: linux (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: linux (Ubuntu Groovy)
Status: New => Invalid
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** No longer affects: linux (Ubuntu Groovy)
** No longer affects: linux (Ubuntu Hirsute)
** No longer affects: linux (Ubuntu Impish)
** Changed in: linux (Ubuntu)
Status: Invalid => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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/1931245
Title:
driver/broadcom/bnxt: invalid dev_port
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Bug description:
[SRU Justification]
[Impact]
With broadcom dual port NIC naming convention between port 1 and port
2 can be inconsistent
For example, if network port 1 of a device is named enp1s0f0, port 2
can end up with the name enp1s0f1d1 rather than enp1s0f1
Issue is due to an inconsistent port_dev and any scripts based on it
can have unexpected behavior
This has been fixed in v5.6 by the following upstream commit
- 1d86859fdf31("bnxt_en: Remove the setting of dev_port")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1d86859fdf31
The bug exists since the beginning of the driver.
== Fix ==
Backport the requested patches to Focal (5.4)
== Risk of Regression ==
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931245/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
Thank you for taking the time to file this bug report. NVIDIA is aware of the problem, and will deliver a fix. In the meantime, we recommend that you use either the nvidia-driver-460-server package or the nvidia-driver-450-server. While -server drivers are usually recommended for datacentres, they also work fine on the desktop. You can read more about this on the following website: https://docs.nvidia.com/datacenter/tesla/index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-465 package in Ubuntu: Triaged Bug description: I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute Jun 03 16:26:57 willow kernel: Oops: [#1] SMP PTI Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P OE 5.11.0-18-generic #19-Ubuntu Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019 Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 R09: 8e318220acb8 Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 R12: 0400 Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 R15: 0800 Jun 03 16:26:57 willow kernel: FS: 7f5807f38a40() GS:8e3466dc() knlGS: Jun 03 16:26:57 willow kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 CR4: 003706e0 Jun 03 16:26:57 willow kernel: DR0: DR1: DR2: Jun 03 16:26:57 willow kernel: DR3: DR6: fffe0ff0 DR7: 0400 Jun 03 16:26:57 willow kernel: Call Trace: Jun 03 16:26:57 willow kernel: ? _nv015556rm+0x7fd/0x1020 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv027155rm+0x22c/0x4f0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017787rm+0x303/0x5e0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017789rm+0xe1/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv022829rm+0xed/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv023065rm+0x30/0x60 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv000704rm+0x16da/0x22b0 [nvidia] Jun 03 16:26:57 willow kernel: ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 03 16:26:57 willow kernel: ? nv_open_device+0x122/0x8e0 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_open+0x2b7/0x560 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 03 16:26:57 willow kernel: ? chrdev_open+0xf7/0x220 Jun 03 16:26:57 willow kernel: ? cdev_device_add+0x90/0x90 Jun 03 16:26:57 willow kernel: ? do_dentry_open+0x156/0x370 Jun 03 16:26:57 willow kernel: ? vfs_open+0x2d/0x30 Jun 03 16:26:57 willow kernel: ? do_open+0x1c3/0x340 Jun 03 16:26:57 willow kernel: ? path_openat+0x10a/0x1d0 Jun 03 16:26:57 willow kernel: ? do_filp_open+0x8c/0x130 Jun 03 16:26:57 willow kernel: ? __check_object_size+0x1c/0x20 Jun 03 16:26:57 willow kernel: ? do_sys_openat2+0x9b/0x150 Jun 03 16:26:57 willow kernel: ? __x64_sys_openat+0x56/0x90 Jun 03 16:26:57 willow kernel: ? do_syscall_64+0x38/0x90 Jun 03 16:26:57 willow kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) > Jun 03 16:26:57 willow kernel: sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c> Jun 03 16:26:57 willow kernel: CR2: 0170 Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]--- Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8
[Kernel-packages] [Bug 1931245] Re: driver/broadcom/bnxt: invalid dev_port
Correction: bug was fixed in v5.6.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Krzysztof Kozlowski (krzk)
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Assignee: Krzysztof Kozlowski (krzk)
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Krzysztof Kozlowski (krzk)
** Changed in: linux (Ubuntu Hirsute)
Assignee: (unassigned) => Krzysztof Kozlowski (krzk)
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Krzysztof Kozlowski (krzk)
** Changed in: linux (Ubuntu Impish)
Status: New => In Progress
** Description changed:
[SRU Justification]
[Impact]
With broadcom dual port NIC naming convention between port 1 and port 2
can be inconsistent
For example, if network port 1 of a device is named enp1s0f0, port 2 can
end up with the name enp1s0f1d1 rather than enp1s0f1
Issue is due to an inconsistent port_dev and any scripts based on it can
have unexpected behavior
- This has been fixed in v5.12 by the following upstream commit
- - 1d86859fdf31("bnxt_en: Remove the setting of dev_port")
+ This has been fixed in v5.6 by the following upstream commit
+ - 1d86859fdf31("bnxt_en: Remove the setting of dev_port")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1d86859fdf31
The bug exists since the beginning of the driver.
== Fix ==
Backport the requested patches to Focal (5.4)
== Risk of Regression ==
The patch is trivial, the potential regressions are low.
--
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/1931245
Title:
driver/broadcom/bnxt: invalid dev_port
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
New
Status in linux source package in Groovy:
New
Status in linux source package in Hirsute:
New
Status in linux source package in Impish:
In Progress
Bug description:
[SRU Justification]
[Impact]
With broadcom dual port NIC naming convention between port 1 and port
2 can be inconsistent
For example, if network port 1 of a device is named enp1s0f0, port 2
can end up with the name enp1s0f1d1 rather than enp1s0f1
Issue is due to an inconsistent port_dev and any scripts based on it
can have unexpected behavior
This has been fixed in v5.6 by the following upstream commit
- 1d86859fdf31("bnxt_en: Remove the setting of dev_port")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1d86859fdf31
The bug exists since the beginning of the driver.
== Fix ==
Backport the requested patches to Focal (5.4)
== Risk of Regression ==
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931245/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931245] Re: driver/broadcom/bnxt: invalid dev_port
For the risk of regression - this paragraph should explain possible
failures, for example if something goes wrong. Even trivial patch can
cause some effects. This one as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1931245
Title:
driver/broadcom/bnxt: invalid dev_port
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
New
Status in linux source package in Groovy:
New
Status in linux source package in Hirsute:
New
Status in linux source package in Impish:
In Progress
Bug description:
[SRU Justification]
[Impact]
With broadcom dual port NIC naming convention between port 1 and port
2 can be inconsistent
For example, if network port 1 of a device is named enp1s0f0, port 2
can end up with the name enp1s0f1d1 rather than enp1s0f1
Issue is due to an inconsistent port_dev and any scripts based on it
can have unexpected behavior
This has been fixed in v5.12 by the following upstream commit
- 1d86859fdf31("bnxt_en: Remove the setting of dev_port")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1d86859fdf31
The bug exists since the beginning of the driver.
== Fix ==
Backport the requested patches to Focal (5.4)
== Risk of Regression ==
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931245/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed
Sent to upstream (LTP): https://github.com/linux-test- project/ltp/pull/829 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829984 Title: memcg_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: startup='Wed May 22 05:59:09 2019' memcg_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 31689 memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 31689 memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4202496, 4194304 expected memcg_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 2 TCONF: mem+swap is not enabled tag=memcg_usage_in_bytes stime=1558504749 dur=1 exit=exited stat=33 core=no cu=5 cs=3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 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: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:17:43 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829979] Re: memcg_max_usage_in_bytes from controllers test suite in LTP failed
Sent to upstream (LTP): https://github.com/linux-test- project/ltp/pull/829 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829979 Title: memcg_max_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Bug description: startup='Wed May 22 05:58:50 2019' memcg_max_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_max_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 1 TINFO: Warming up pid: 30821 memcg_max_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 30821 memcg_max_usage_in_bytes_test 1 TFAIL: memory.max_usage_in_bytes is 4325376, 4194304 expected memcg_max_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TCONF: mem+swap is not enabled memcg_max_usage_in_bytes_test 2 TINFO: Starting test 3 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 2 TINFO: Warming up pid: 30855 memcg_max_usage_in_bytes_test 2 TINFO: Process is still here after warm up: 30855 memcg_max_usage_in_bytes_test 2 TFAIL: memory.max_usage_in_bytes is 4329472, 4194304 expected memcg_max_usage_in_bytes_test 3 TFAIL: memory.max_usage_in_bytes is 8192, 0 expected memcg_max_usage_in_bytes_test 4 TINFO: Starting test 4 sh: echo: I/O error memcg_max_usage_in_bytes_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 4 TCONF: mem+swap is not enabled tag=memcg_max_usage_in_bytes stime=1558504730 dur=3 exit=exited stat=33 core=no cu=8 cs=7 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 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: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:06:31 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929147] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1929147 Title: fix system hang with 5.10 kernel + RX540 on RKL platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Committed Bug description: [Impact] On RKL platform with AMD RX540, system would hang during boot-up. [Fix] AMD introduce a brand new firmware, polaris 12 MC firmware. This fix the issue and the system wouldn't hang during boot-up with AMD RX540. [Test] Verified on RKL platform and AMD RX540 System would boot-up and login to desktop successfully. [Where problems could occur] This's a brand new firmware to support Polaris-series, it may introduce new issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926236] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1926236 Title: Fix The sound has noise while audio volume is maximum Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Bug description: [Impact] The sound has noise while turning the audio volume to maximum [Fix] For VEGA & Polaris, need two patches(landed on mainline kernel) to fix and a modprobe 1.(50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 2.(9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on oem kernel 3. #modprobe amdgpu ppfeaturemask=0xfff7bffb. For Navi_1x, need smc firmware to fix. 1. (4fe6e53b96 linux-firmware) amdgpu: update navi10 SMC firmware 1. (8ab7abaf63 linux-firmware) amdgpu: update navi14 SMC firmware [Test] Verified on RKL platform A. with wx3200(Polaris series) and the following configuration 1. With these two patch, 1.1. (50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 1.2. (9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on oem kernel 2. doesn't append ppfeaturemask=0xfff7bffb Can't observe issue. B. With wx5500(Navi series) and update the related firmware, Can't observe issue [Where problems could occur] Because disabling DPM, the power consumption would be slightly higher. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926236] Re: Fix The sound has noise while audio volume is maximum
This bug was fixed in the package linux-firmware - 1.187.14 --- linux-firmware (1.187.14) focal; urgency=medium * Fix system hang with 5.10 kernel + RX540 on RKL platform (LP: #1929147) - amdgpu: add new polaris 12 MC firmware linux-firmware (1.187.13) focal; urgency=medium * Fix noisy audio when volume is at maximum (LP: #1926236) - amdgpu: update navi14 smc firmware - amdgpu: update navi10 SMC firmware -- Seth Forshee Fri, 28 May 2021 09:47:39 -0500 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1926236 Title: Fix The sound has noise while audio volume is maximum Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Bug description: [Impact] The sound has noise while turning the audio volume to maximum [Fix] For VEGA & Polaris, need two patches(landed on mainline kernel) to fix and a modprobe 1.(50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 2.(9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on oem kernel 3. #modprobe amdgpu ppfeaturemask=0xfff7bffb. For Navi_1x, need smc firmware to fix. 1. (4fe6e53b96 linux-firmware) amdgpu: update navi10 SMC firmware 1. (8ab7abaf63 linux-firmware) amdgpu: update navi14 SMC firmware [Test] Verified on RKL platform A. with wx3200(Polaris series) and the following configuration 1. With these two patch, 1.1. (50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 1.2. (9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on oem kernel 2. doesn't append ppfeaturemask=0xfff7bffb Can't observe issue. B. With wx5500(Navi series) and update the related firmware, Can't observe issue [Where problems could occur] Because disabling DPM, the power consumption would be slightly higher. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929147] Re: fix system hang with 5.10 kernel + RX540 on RKL platform
This bug was fixed in the package linux-firmware - 1.187.14 --- linux-firmware (1.187.14) focal; urgency=medium * Fix system hang with 5.10 kernel + RX540 on RKL platform (LP: #1929147) - amdgpu: add new polaris 12 MC firmware linux-firmware (1.187.13) focal; urgency=medium * Fix noisy audio when volume is at maximum (LP: #1926236) - amdgpu: update navi14 smc firmware - amdgpu: update navi10 SMC firmware -- Seth Forshee Fri, 28 May 2021 09:47:39 -0500 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1929147 Title: fix system hang with 5.10 kernel + RX540 on RKL platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Committed Bug description: [Impact] On RKL platform with AMD RX540, system would hang during boot-up. [Fix] AMD introduce a brand new firmware, polaris 12 MC firmware. This fix the issue and the system wouldn't hang during boot-up with AMD RX540. [Test] Verified on RKL platform and AMD RX540 System would boot-up and login to desktop successfully. [Where problems could occur] This's a brand new firmware to support Polaris-series, it may introduce new issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829979] Re: memcg_max_usage_in_bytes from controllers test suite in LTP failed
** Changed in: ubuntu-kernel-tests Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829979 Title: memcg_max_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Bug description: startup='Wed May 22 05:58:50 2019' memcg_max_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_max_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 1 TINFO: Warming up pid: 30821 memcg_max_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 30821 memcg_max_usage_in_bytes_test 1 TFAIL: memory.max_usage_in_bytes is 4325376, 4194304 expected memcg_max_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TCONF: mem+swap is not enabled memcg_max_usage_in_bytes_test 2 TINFO: Starting test 3 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 2 TINFO: Warming up pid: 30855 memcg_max_usage_in_bytes_test 2 TINFO: Process is still here after warm up: 30855 memcg_max_usage_in_bytes_test 2 TFAIL: memory.max_usage_in_bytes is 4329472, 4194304 expected memcg_max_usage_in_bytes_test 3 TFAIL: memory.max_usage_in_bytes is 8192, 0 expected memcg_max_usage_in_bytes_test 4 TINFO: Starting test 4 sh: echo: I/O error memcg_max_usage_in_bytes_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 4 TCONF: mem+swap is not enabled tag=memcg_max_usage_in_bytes stime=1558504730 dur=3 exit=exited stat=33 core=no cu=8 cs=7 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 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: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:06:31 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed
** Changed in: ubuntu-kernel-tests Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829984 Title: memcg_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: startup='Wed May 22 05:59:09 2019' memcg_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 31689 memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 31689 memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4202496, 4194304 expected memcg_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 2 TCONF: mem+swap is not enabled tag=memcg_usage_in_bytes stime=1558504749 dur=1 exit=exited stat=33 core=no cu=5 cs=3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 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: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:17:43 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892165] Re: futex_wake04 from ubuntu_ltp_syscalls failed on X i386
https://lists.linux.it/pipermail/ltp/2021-June/023076.html ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Won't Fix => Invalid ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: ubuntu-kernel-tests Status: New => In Progress -- 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/1892165 Title: futex_wake04 from ubuntu_ltp_syscalls failed on X i386 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Invalid Bug description: Issue found on Xenial i386 node "pepe" with 4.4.0-189.219 generic / low-latency (passed on other arches) <<>> tag=futex_wake04 stime=1597828807 cmdline="futex_wake04" contacts="" analysis=exit <<>> incrementing stop tst_hugepage.c:58: INFO: 1 hugepage(s) reserved tst_test.c:1250: INFO: Timeout per run is 0h 05m 00s futex_wake04.c:60: INFO: Testing variant: syscall with old kernel spec futex_wake04.c:98: INFO: Hugepagesize 2097152 futex_utils.h:51: INFO: Thread 13011 not sleeping yet futex_wake04.c:85: FAIL: Bug: wait_thread2 did not wake after 30 secs.: EINVAL (22) futex_utils.h:62: INFO: 0 threads sleeping, expected 2 tst_test.c:1250: INFO: Timeout per run is 0h 05m 00s futex_wake04.c:60: INFO: Testing variant: syscall time64 with kernel spec ../../../../include/tst_timer.h:261: CONF: syscall(422) __NR_futex_time64 not supported Summary: passed 0 failed 1 skipped 1 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=33 corefile=no cutime=0 cstime=4 <<>> This can be reproduced on 4.4.0-187-generic as well, not a regression. Possibly cause by commit https://github.com/linux-test- project/ltp/commit/8d2c9c7d597c4b220c52bbbd0ab849ece86fe12c in LTP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Can you narrow down which specific firmware file causes the problem? We haven't been able to repro this. I think it may be related to a change in mesa. Specifically mesa commit 820dec3f7c7. For more info see https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #4866 https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931245] Re: driver/broadcom/bnxt: invalid dev_port
** Project changed: canonical-identity-provider => 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/1931245
Title:
driver/broadcom/bnxt: invalid dev_port
Status in linux package in Ubuntu:
New
Bug description:
[SRU Justification]
[Impact]
With broadcom dual port NIC naming convention between port 1 and port
2 can be inconsistent
For example, if network port 1 of a device is named enp1s0f0, port 2
can end up with the name enp1s0f1d1 rather than enp1s0f1
Issue is due to an inconsistent port_dev and any scripts based on it
can have unexpected behavior
This has been fixed in v5.12 by the following upstream commit
- 1d86859fdf31("bnxt_en: Remove the setting of dev_port")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1d86859fdf31
The bug exists since the beginning of the driver.
== Fix ==
Backport the requested patches to Focal (5.4)
== Risk of Regression ==
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931245/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931245] [NEW] driver/broadcom/bnxt: invalid dev_port
You have been subscribed to a public bug:
[SRU Justification]
[Impact]
With broadcom dual port NIC naming convention between port 1 and port 2
can be inconsistent
For example, if network port 1 of a device is named enp1s0f0, port 2 can
end up with the name enp1s0f1d1 rather than enp1s0f1
Issue is due to an inconsistent port_dev and any scripts based on it can
have unexpected behavior
This has been fixed in v5.12 by the following upstream commit
- 1d86859fdf31("bnxt_en: Remove the setting of dev_port")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1d86859fdf31
The bug exists since the beginning of the driver.
== Fix ==
Backport the requested patches to Focal (5.4)
== Risk of Regression ==
The patch is trivial, the potential regressions are low.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
driver/broadcom/bnxt: invalid dev_port
https://bugs.launchpad.net/bugs/1931245
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 1892165] Re: futex_wake04 from ubuntu_ltp_syscalls failed on X i386
This is looking more like a test issue on 32-bit, so no need to blacklist it on xenial, as we get the test fixed. :-) Cascardo. -- 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/1892165 Title: futex_wake04 from ubuntu_ltp_syscalls failed on X i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Won't Fix Status in linux source package in Bionic: New Bug description: Issue found on Xenial i386 node "pepe" with 4.4.0-189.219 generic / low-latency (passed on other arches) <<>> tag=futex_wake04 stime=1597828807 cmdline="futex_wake04" contacts="" analysis=exit <<>> incrementing stop tst_hugepage.c:58: INFO: 1 hugepage(s) reserved tst_test.c:1250: INFO: Timeout per run is 0h 05m 00s futex_wake04.c:60: INFO: Testing variant: syscall with old kernel spec futex_wake04.c:98: INFO: Hugepagesize 2097152 futex_utils.h:51: INFO: Thread 13011 not sleeping yet futex_wake04.c:85: FAIL: Bug: wait_thread2 did not wake after 30 secs.: EINVAL (22) futex_utils.h:62: INFO: 0 threads sleeping, expected 2 tst_test.c:1250: INFO: Timeout per run is 0h 05m 00s futex_wake04.c:60: INFO: Testing variant: syscall time64 with kernel spec ../../../../include/tst_timer.h:261: CONF: syscall(422) __NR_futex_time64 not supported Summary: passed 0 failed 1 skipped 1 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=33 corefile=no cutime=0 cstime=4 <<>> This can be reproduced on 4.4.0-187-generic as well, not a regression. Possibly cause by commit https://github.com/linux-test- project/ltp/commit/8d2c9c7d597c4b220c52bbbd0ab849ece86fe12c in LTP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
I've built a kernel to map the MIC-MUTE key (Fn+F4) in https://people.canonical.com/~mschiu77/lp1927545/. Could you help test the mic mute function and give me the dmesg output when you press Fn+F4? Thanks The Fn+F10 (Scissors) is probably MS Windows specific. I can't find an appropriate mapping for it so I'll leave it as-is. -- 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/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I found that some of the Lenovo Lenovo Essential Wireless Keyboard Fn keys don't work. First one is Mute mic (Fn+F4), second one is Scissors (Fn+F10, probably hotkey for Windows Snipping Tool for selective screenshot).gnome-control-panel, xev and evtest doesn't react on pressing these buttons. Here what I was able to get via sudo cat /dev/usb/hiddev0 | hexdump -v -e '/1 "%02X\n"' : For Mute key 00 00 00 FF DC 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 For Scissors 00 00 00 FF DB 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asudak 2085 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 6 22:36:50 2021 InstallationDate: Installed on 2021-04-13 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-18 (17 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892165] Re: futex_wake04 from ubuntu_ltp_syscalls failed on X i386
OK Cascardo, I will blacklist this test on Xenial later. Thanks! -- 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/1892165 Title: futex_wake04 from ubuntu_ltp_syscalls failed on X i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Won't Fix Status in linux source package in Bionic: New Bug description: Issue found on Xenial i386 node "pepe" with 4.4.0-189.219 generic / low-latency (passed on other arches) <<>> tag=futex_wake04 stime=1597828807 cmdline="futex_wake04" contacts="" analysis=exit <<>> incrementing stop tst_hugepage.c:58: INFO: 1 hugepage(s) reserved tst_test.c:1250: INFO: Timeout per run is 0h 05m 00s futex_wake04.c:60: INFO: Testing variant: syscall with old kernel spec futex_wake04.c:98: INFO: Hugepagesize 2097152 futex_utils.h:51: INFO: Thread 13011 not sleeping yet futex_wake04.c:85: FAIL: Bug: wait_thread2 did not wake after 30 secs.: EINVAL (22) futex_utils.h:62: INFO: 0 threads sleeping, expected 2 tst_test.c:1250: INFO: Timeout per run is 0h 05m 00s futex_wake04.c:60: INFO: Testing variant: syscall time64 with kernel spec ../../../../include/tst_timer.h:261: CONF: syscall(422) __NR_futex_time64 not supported Summary: passed 0 failed 1 skipped 1 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=33 corefile=no cutime=0 cstime=4 <<>> This can be reproduced on 4.4.0-187-generic as well, not a regression. Possibly cause by commit https://github.com/linux-test- project/ltp/commit/8d2c9c7d597c4b220c52bbbd0ab849ece86fe12c in LTP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892165/+subscriptions -- Mailing list: https://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 1930925] Re: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch
I don't have a "Unifying receiver". That's just the name which appears and/or disappears when I plug in the KVM to the PC. The KVM in all cases is directly connected to the keyboard/mouse/screen at one end, and USB ports/HDMI at the PC end. -- Original Message -- From: "Hui Wang" <1930...@bugs.launchpad.net> To: j...@pobox.com Sent: 08/06/2021 11:21:35 Subject: [Bug 1930925] Re: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch >Please plug the Unifying Receiver to the usb port of 20.04 machine >directly (the usb port which connects to the KVM switch), then run lsusb >and upload the output. > >Let us compare the log with the one you plug the Unifying Receiver to >the usb port of KVM switch. > >-- >You received this bug notification because you are subscribed to the bug >report. >https://bugs.launchpad.net/bugs/1930925 > >Title: > Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a > KVM switch > >Status in linux package in Ubuntu: > New > >Bug description: > I have recently acquired a acquired a desktop running ubuntu 20.04. I > have several computers and switch between them using this KVM >https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 > The other machines are either running windows or ubuntu 18.04 or > earlier. They are all fine, but the with 20.04 machine neither the > keyboard nor the mouse works. On the 18.04 machine I can see > > lsusb > Bus 002 Device 002: ID 8087:8000 Intel Corp. > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 002: ID 8087:8008 Intel Corp. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > and it is the Logitech, Inc. Unifying Receiver which appears when the > USB from the KVM is connected. On the 20.04 machine only this appears > > lsusb > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller > Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > I have tested installation discs from 19.04 onwards. The failure first > appears in 19.10 and is still present in 21.04 > > I can observe a similar problem with a dual boot laptop running > windows 10 and 20.04. With windows 10 I can use it with the KVM for > screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and > mouse do not work. This issue has also been observed here >https://unix.stackexchange.com/questions/646515/using-logitech-mouse- > keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed > it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model). > > I had to report this originally against xorg as this bug reporting > system seems not to allow reporting of bugs against unknown packages. > I also had to report it through the ubuntu-bug executable as I've been > unable to find a way in launchpad of reporting a bug (as opposed to > getting a guided tour about reporting bugs). > > I am happy to supply more info and test fixes if I am asked but as > with this type of bug where something fails to happen rather than > something wrong happens I don't know what to look at. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-53-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > Date: Fri Jun 4 20:21:15 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DpkgLog: > > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. Device [1043:8694] > InstallationDate: Installed on 2021-05-14 (21 days ago) > InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 > (20210209.1) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller >Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Lsusb-t: >/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M >/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M >|__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M >|__ Port 13: Dev 3, If 0, Class=Vendor Specific Class, Driver=,
[Kernel-packages] [Bug 1829979] Re: memcg_max_usage_in_bytes from controllers test suite in LTP failed
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Krzysztof Kozlowski (krzk) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829979 Title: memcg_max_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Bug description: startup='Wed May 22 05:58:50 2019' memcg_max_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_max_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 1 TINFO: Warming up pid: 30821 memcg_max_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 30821 memcg_max_usage_in_bytes_test 1 TFAIL: memory.max_usage_in_bytes is 4325376, 4194304 expected memcg_max_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TCONF: mem+swap is not enabled memcg_max_usage_in_bytes_test 2 TINFO: Starting test 3 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 2 TINFO: Warming up pid: 30855 memcg_max_usage_in_bytes_test 2 TINFO: Process is still here after warm up: 30855 memcg_max_usage_in_bytes_test 2 TFAIL: memory.max_usage_in_bytes is 4329472, 4194304 expected memcg_max_usage_in_bytes_test 3 TFAIL: memory.max_usage_in_bytes is 8192, 0 expected memcg_max_usage_in_bytes_test 4 TINFO: Starting test 4 sh: echo: I/O error memcg_max_usage_in_bytes_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 4 TCONF: mem+swap is not enabled tag=memcg_max_usage_in_bytes stime=1558504730 dur=3 exit=exited stat=33 core=no cu=8 cs=7 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 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: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:06:31 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Krzysztof Kozlowski (krzk) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829984 Title: memcg_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: startup='Wed May 22 05:59:09 2019' memcg_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 31689 memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 31689 memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4202496, 4194304 expected memcg_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 2 TCONF: mem+swap is not enabled tag=memcg_usage_in_bytes stime=1558504749 dur=1 exit=exited stat=33 core=no cu=5 cs=3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 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: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:17:43 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829984/+subscriptions -- Mailing list: https://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 1930925] Re: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch
Neither. I tested all the distros on an old machine I have which currently runs windows 10. The distros were tested by putting the installation on a DVD and booting from it. Here's what windows claims it has Device namefeit ProcessorIntel(R) Core(TM) i7-2700K CPU @ 3.50GHz 3.50 GHz Installed RAM16.0 GB Device ID86452CEC-D6C1-46A6-9970-7FE2338F4B02 Product ID00326-1-0-AA334 System type64-bit operating system, x64-based processor Pen and touchNo pen or touch input is available for this display Here's the motherboard info C:\Users\Jon>wmic baseboard get product,Manufacturer,version,serialnumber Manufacturer Product SerialNumber Version Intel Corporation DH67BL BTBL13400AKJ AAG10189-209 I can't find an easy way to copy the USB info, so here's a screenshot (attached) -- Original Message -- From: "Hui Wang" <1930...@bugs.launchpad.net> To: j...@pobox.com Sent: 08/06/2021 11:24:28 Subject: [Bug 1930925] Re: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch >BTW, you said you tested 19.10 and onwards, did you test them on that >20.04 machine (ASuS machine) or the 18.04 machine? > >-- >You received this bug notification because you are subscribed to the bug >report. >https://bugs.launchpad.net/bugs/1930925 > >Title: > Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a > KVM switch > >Status in linux package in Ubuntu: > New > >Bug description: > I have recently acquired a acquired a desktop running ubuntu 20.04. I > have several computers and switch between them using this KVM >https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 > The other machines are either running windows or ubuntu 18.04 or > earlier. They are all fine, but the with 20.04 machine neither the > keyboard nor the mouse works. On the 18.04 machine I can see > > lsusb > Bus 002 Device 002: ID 8087:8000 Intel Corp. > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 002: ID 8087:8008 Intel Corp. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > and it is the Logitech, Inc. Unifying Receiver which appears when the > USB from the KVM is connected. On the 20.04 machine only this appears > > lsusb > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller > Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > I have tested installation discs from 19.04 onwards. The failure first > appears in 19.10 and is still present in 21.04 > > I can observe a similar problem with a dual boot laptop running > windows 10 and 20.04. With windows 10 I can use it with the KVM for > screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and > mouse do not work. This issue has also been observed here >https://unix.stackexchange.com/questions/646515/using-logitech-mouse- > keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed > it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model). > > I had to report this originally against xorg as this bug reporting > system seems not to allow reporting of bugs against unknown packages. > I also had to report it through the ubuntu-bug executable as I've been > unable to find a way in launchpad of reporting a bug (as opposed to > getting a guided tour about reporting bugs). > > I am happy to supply more info and test fixes if I am asked but as > with this type of bug where something fails to happen rather than > something wrong happens I don't know what to look at. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-53-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > Date: Fri Jun 4 20:21:15 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DpkgLog: > > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. Device [1043:8694] > InstallationDate: Installed on 2021-05-14 (21 days ago) > InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 > (20210209.1) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Co
[Kernel-packages] [Bug 1931240] Re: Intel ADL-S graphics feature enabling
SRU: https://lists.ubuntu.com/archives/kernel-team/2021-June/121162.html
(oem-5.13, impish)
--
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/1931240
Title:
Intel ADL-S graphics feature enabling
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Bug description:
[SRU Justfication]
[Impact]
While all other ADL-S i915 commits have been included in v5.13-rc1, the
last one missed the train is to add two more PCI IDs.
[Fix]
Commit 3f50033dd88a ("drm/i915/adl_s: ADL-S platform Update PCI ids for
Mobile BGA") that is currently in drm-intel, branch for-linux-next.
[Test Case]
With this patch, i915 kernel module should be automatically probed.
[Where problems could occur]
While this is part of the initial support for i915 on ADL-S platforms,
the hardware to be enabled could still be unstable and feature laking.
But since this patch only addes two additional PCI IDs to the new
family, it should not introduce any regression to the exsiting ones.
[Other Info]
ADL-S support targets kernel version 5.13, so only unstable and oem-5.13
will be nominated for this fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931240/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931242] [NEW] linux-uc20-efi: make it easy to build derivative kernel.efi
Public bug reported: linux-uc20-efi: make it easy to build derivative kernel.efi Currently debian/rules & debian.uc20-efi/control.stub are tightly coupled and hardcode the source package name (linux-uc20-efi), its relationship to linux-unsigned-image-* packages, and flavours to build kernel.efi apps for. Decouple those things a little bit, to make it easier to build derivative kernel.efi apps. 1) do not calculate KERNEL_SOURCE variable at all, as it is not needed 2) calculate flavours to build kernel.efi for, from build-deps This allows to create a derivative linux-blah-uc20-efi, and simply adjust debian.blah-uc20-efi/control.stub and produce correct signing tarballs for the correct required derivative flavour. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931242 Title: linux-uc20-efi: make it easy to build derivative kernel.efi Status in linux package in Ubuntu: New Bug description: linux-uc20-efi: make it easy to build derivative kernel.efi Currently debian/rules & debian.uc20-efi/control.stub are tightly coupled and hardcode the source package name (linux-uc20-efi), its relationship to linux-unsigned-image-* packages, and flavours to build kernel.efi apps for. Decouple those things a little bit, to make it easier to build derivative kernel.efi apps. 1) do not calculate KERNEL_SOURCE variable at all, as it is not needed 2) calculate flavours to build kernel.efi for, from build-deps This allows to create a derivative linux-blah-uc20-efi, and simply adjust debian.blah-uc20-efi/control.stub and produce correct signing tarballs for the correct required derivative flavour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931240] Re: Intel ADL-S graphics feature enabling
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1923551
--
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/1931240
Title:
Intel ADL-S graphics feature enabling
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Bug description:
[SRU Justfication]
[Impact]
While all other ADL-S i915 commits have been included in v5.13-rc1, the
last one missed the train is to add two more PCI IDs.
[Fix]
Commit 3f50033dd88a ("drm/i915/adl_s: ADL-S platform Update PCI ids for
Mobile BGA") that is currently in drm-intel, branch for-linux-next.
[Test Case]
With this patch, i915 kernel module should be automatically probed.
[Where problems could occur]
While this is part of the initial support for i915 on ADL-S platforms,
the hardware to be enabled could still be unstable and feature laking.
But since this patch only addes two additional PCI IDs to the new
family, it should not introduce any regression to the exsiting ones.
[Other Info]
ADL-S support targets kernel version 5.13, so only unstable and oem-5.13
will be nominated for this fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931240/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931240] [NEW] Intel ADL-S graphics feature enabling
Public bug reported:
[SRU Justfication]
[Impact]
While all other ADL-S i915 commits have been included in v5.13-rc1, the
last one missed the train is to add two more PCI IDs.
[Fix]
Commit 3f50033dd88a ("drm/i915/adl_s: ADL-S platform Update PCI ids for
Mobile BGA") that is currently in drm-intel, branch for-linux-next.
[Test Case]
With this patch, i915 kernel module should be automatically probed.
[Where problems could occur]
While this is part of the initial support for i915 on ADL-S platforms,
the hardware to be enabled could still be unstable and feature laking.
But since this patch only addes two additional PCI IDs to the new
family, it should not introduce any regression to the exsiting ones.
[Other Info]
ADL-S support targets kernel version 5.13, so only unstable and oem-5.13
will be nominated for this fix.
** Affects: linux (Ubuntu)
Importance: High
Assignee: You-Sheng Yang (vicamo)
Status: In Progress
** Affects: linux-oem-5.13 (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Status: Invalid
** Affects: linux-oem-5.13 (Ubuntu Focal)
Importance: High
Assignee: You-Sheng Yang (vicamo)
Status: In Progress
** Affects: linux (Ubuntu Impish)
Importance: High
Assignee: You-Sheng Yang (vicamo)
Status: In Progress
** Affects: linux-oem-5.13 (Ubuntu Impish)
Importance: Undecided
Status: Invalid
** Tags: hwe-graphics ihv-intel
** Also affects: linux-oem-5.13 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.13 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Assignee: You-Sheng Yang (vicamo)
Status: New
** Also affects: linux-oem-5.13 (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux (Ubuntu Impish)
Status: New => In Progress
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => High
** Changed in: linux (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux-oem-5.13 (Ubuntu Impish)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1931240
Title:
Intel ADL-S graphics feature enabling
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Bug description:
[SRU Justfication]
[Impact]
While all other ADL-S i915 commits have been included in v5.13-rc1, the
last one missed the train is to add two more PCI IDs.
[Fix]
Commit 3f50033dd88a ("drm/i915/adl_s: ADL-S platform Update PCI ids for
Mobile BGA") that is currently in drm-intel, branch for-linux-next.
[Test Case]
With this patch, i915 kernel module should be automatically probed.
[Where problems could occur]
While this is part of the initial support for i915 on ADL-S platforms,
the hardware to be enabled could still be unstable and feature laking.
But since this patch only addes two additional PCI IDs to the new
family, it should not introduce any regression to the exsiting ones.
[Other Info]
ADL-S support targets kernel version 5.13, so only unstable and oem-5.13
will be nominated for this fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931240/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892165] Re: futex_wake04 from ubuntu_ltp_syscalls failed on X i386
Hi, PHLin. I have done some work on futex recently, I can take a look at this on bionic, since we are not going to fix it on xenial. Cascardo. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- 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/1892165 Title: futex_wake04 from ubuntu_ltp_syscalls failed on X i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Won't Fix Status in linux source package in Bionic: New Bug description: Issue found on Xenial i386 node "pepe" with 4.4.0-189.219 generic / low-latency (passed on other arches) <<>> tag=futex_wake04 stime=1597828807 cmdline="futex_wake04" contacts="" analysis=exit <<>> incrementing stop tst_hugepage.c:58: INFO: 1 hugepage(s) reserved tst_test.c:1250: INFO: Timeout per run is 0h 05m 00s futex_wake04.c:60: INFO: Testing variant: syscall with old kernel spec futex_wake04.c:98: INFO: Hugepagesize 2097152 futex_utils.h:51: INFO: Thread 13011 not sleeping yet futex_wake04.c:85: FAIL: Bug: wait_thread2 did not wake after 30 secs.: EINVAL (22) futex_utils.h:62: INFO: 0 threads sleeping, expected 2 tst_test.c:1250: INFO: Timeout per run is 0h 05m 00s futex_wake04.c:60: INFO: Testing variant: syscall time64 with kernel spec ../../../../include/tst_timer.h:261: CONF: syscall(422) __NR_futex_time64 not supported Summary: passed 0 failed 1 skipped 1 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=33 corefile=no cutime=0 cstime=4 <<>> This can be reproduced on 4.4.0-187-generic as well, not a regression. Possibly cause by commit https://github.com/linux-test- project/ltp/commit/8d2c9c7d597c4b220c52bbbd0ab849ece86fe12c in LTP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930925] Re: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch
BTW, you said you tested 19.10 and onwards, did you test them on that 20.04 machine (ASuS machine) or the 18.04 machine? -- 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/1930925 Title: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch Status in linux package in Ubuntu: New Bug description: I have recently acquired a acquired a desktop running ubuntu 20.04. I have several computers and switch between them using this KVM https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 The other machines are either running windows or ubuntu 18.04 or earlier. They are all fine, but the with 20.04 machine neither the keyboard nor the mouse works. On the 18.04 machine I can see lsusb Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub and it is the Logitech, Inc. Unifying Receiver which appears when the USB from the KVM is connected. On the 20.04 machine only this appears lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I have tested installation discs from 19.04 onwards. The failure first appears in 19.10 and is still present in 21.04 I can observe a similar problem with a dual boot laptop running windows 10 and 20.04. With windows 10 I can use it with the KVM for screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and mouse do not work. This issue has also been observed here https://unix.stackexchange.com/questions/646515/using-logitech-mouse- keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model). I had to report this originally against xorg as this bug reporting system seems not to allow reporting of bugs against unknown packages. I also had to report it through the ubuntu-bug executable as I've been unable to find a way in launchpad of reporting a bug (as opposed to getting a guided tour about reporting bugs). I am happy to supply more info and test fixes if I am asked but as with this type of bug where something fails to happen rather than something wrong happens I don't know what to look at. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Jun 4 20:21:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-05-14 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 13: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 13: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=0c391c11-c570-4e04-a351-4fd128a75369 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2021 dmi.bios.release: 8.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0820 dmi.board.asset.tag: Default string dmi.board.name: PRIME H570M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.vers
[Kernel-packages] [Bug 1930925] Re: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch
Please plug the Unifying Receiver to the usb port of 20.04 machine directly (the usb port which connects to the KVM switch), then run lsusb and upload the output. Let us compare the log with the one you plug the Unifying Receiver to the usb port of KVM switch. -- 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/1930925 Title: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch Status in linux package in Ubuntu: New Bug description: I have recently acquired a acquired a desktop running ubuntu 20.04. I have several computers and switch between them using this KVM https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 The other machines are either running windows or ubuntu 18.04 or earlier. They are all fine, but the with 20.04 machine neither the keyboard nor the mouse works. On the 18.04 machine I can see lsusb Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub and it is the Logitech, Inc. Unifying Receiver which appears when the USB from the KVM is connected. On the 20.04 machine only this appears lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I have tested installation discs from 19.04 onwards. The failure first appears in 19.10 and is still present in 21.04 I can observe a similar problem with a dual boot laptop running windows 10 and 20.04. With windows 10 I can use it with the KVM for screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and mouse do not work. This issue has also been observed here https://unix.stackexchange.com/questions/646515/using-logitech-mouse- keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model). I had to report this originally against xorg as this bug reporting system seems not to allow reporting of bugs against unknown packages. I also had to report it through the ubuntu-bug executable as I've been unable to find a way in launchpad of reporting a bug (as opposed to getting a guided tour about reporting bugs). I am happy to supply more info and test fixes if I am asked but as with this type of bug where something fails to happen rather than something wrong happens I don't know what to look at. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Jun 4 20:21:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-05-14 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 13: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 13: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=0c391c11-c570-4e04-a351-4fd128a75369 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2021 dmi.bios.release: 8.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0820 dmi.board.asset.tag: Default string dmi.board.name: PRIME H570M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.b
[Kernel-packages] [Bug 1929255] Re: update-initrd-links creates incorrect symlinks
Is something going to be done to fix the regressions reported for Bionic and Focal ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1929255 Title: update-initrd-links creates incorrect symlinks Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Groovy: New Status in linux-base source package in Hirsute: Fix Committed Status in linux-base source package in Impish: Fix Released Bug description: [Impact] ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. [Test Plan] * Install new linux-base and initramfs-tools * create /etc/kernel-img.conf with do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = yes * Install one kernel flavour, check that symlinks in /boot have sane targets * Install another kernel, check that symlinks in /boot/ have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it). and check that symlinks in /boot have sane targets. * Purge all kernel, and remove symlinks in /boot * Update /etc/kernel-img.conf to do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no * Install one kernel flavour, check that symlinks in / have sane targets * Install another kernel, check that symlinks in / have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it) * remove all kernels, purge initramfs-tools, clean up symlinks in / and /boot * repeat all of the above, without having initramfs-tools installed. I.e. install kernels _without_ recommneds. [Where problems could occur] * The rewritten postinst.d script now simply mostly calls linux- update-links like the normal linux-image postinst script does. One has to make sure that .deb installations of kernels happens correctly and that installkernel way of installing kernels happens correctly. Under different kernel-img.conf settings. The previous incarnations of fixing this and related issues did not account for the above cases and codepaths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+subscriptions -- Mailing list: https://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 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
first off don't take my word that fan control doesn't work i'm slightly out of my depth! if fan control doesn't work is 84c the actual temp or an ideal temp? also have attached log debug output for latest master. ta On 08/06/2021 02:08, Srinivas Pandruvada wrote: > I wish fan control worked. > I release v2.4.6 with the changes. This is in master branch with tag v2.4.6. > There are three commits on top of v2.4.5 to address this issue. > > Please try. > ** Attachment added: "newmaster-output.txt" https://bugs.launchpad.net/bugs/1930422/+attachment/5503112/+files/newmaster-output.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system Status in thermald package in Ubuntu: New Bug description: cpu runs at 100c fan at 3000rpm when in heavy use previous version was ok re: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186 lshw -short is: H/W path Device Class Description == system XPS 8940 (09C5) /0 bus0KV3RP /0/0memory 64KiB BIOS /0/9memory 16GiB System Memory /0/9/0 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/1 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/2 memory Project-Id-Version: lshwRepor /0/9/3 memory Project-Id-Version: lshwRepor /0/35 memory 512KiB L1 cache /0/36 memory 2MiB L2 cache /0/37 memory 16MiB L3 cache /0/38 processor Intel(R) Core(TM) i7-10700 CP /0/100 bridge Intel Corporation /0/100/1bridge Xeon E3-1200 v5/E3-1500 v5/6t /0/100/1/0 displayTU106 [GeForce RTX 2060 Rev. /0/100/1/0.1multimedia TU106 High Definition Audio C /0/100/1/0.2busTU106 USB 3.1 Host Controller /0/100/1/0.2/0 usb3 busxHCI Host Controller /0/100/1/0.2/1 usb4 busxHCI Host Controller /0/100/1/0.3busTU106 USB Type-C UCSI Control /0/100/2displayIntel Corporation /0/100/4genericXeon E3-1200 v5/E3-1500 v5/6t /0/100/8genericXeon E3-1200 v5/v6 / E3-1500 /0/100/12 genericComet Lake PCH Thermal Contro /0/100/14 busComet Lake USB 3.1 xHCI Host /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/4 enx0c5b8f279a64 communication HUAWEI_MOBILE /0/100/14/0/5 input Dell MS116 USB Optical Mouse /0/100/14/0/6 input Dell KB216 Wired Keyboard /0/100/14/0/b genericUSB2.0-CRW /0/100/14/0/c genericUB91C /0/100/14/0/e communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3wlo1 networkWi-Fi 6 AX201 /0/100/15 busComet Lake PCH Serial IO I2C /0/100/16 communication Comet Lake HECI Controller /0/100/17 storageIntel Corporation /0/100/1b bridge Comet Lake PCI Express Root P /0/100/1b/0 storageSamsung Electronics Co Ltd /0/100/1b/0/0 /dev/nvme0 storagePM991 NVMe Samsung 512GB /0/100/1b/0/0/1/dev/nvme0n1 disk 512GB NVMe namespace /0/100/1b/0/0/1/1 volume 149MiB Windows FAT volume /0/100/1b/0/0/1/2 /dev/nvme0n1p2 volume 127MiB reserved partition /0/100/1b/0/0/1/3 /dev/nvme0n1p3 volume 214GiB Windows NTFS volume /0/100/1b/0/0/1/4 /dev/nvme0n1p4 volume 989MiB Windows NTFS volume /0/100/1b/0/0/1/5 /dev/nvme0n1p5 volume 16GiB Windows NTFS volume /0/100/1b/0/0/1/6 /dev/nvme0n1p6 volume 1417MiB Windows NTFS volume /0/100/1b/0/0/1/7 /dev/nvme0n1p7 volume 243GiB EXT4 volume /0/100/1c bridge Intel Corporation
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.11.0.1007.7)
All autopkgtests for the newly accepted linux-meta-azure (5.11.0.1007.7) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916517] Re: ERROR: Kernel configuration is invalid. include/generated/autoconf.h or include/config/auto.conf are missing.
I had a similar issue after upgrading to 21.04. Package linux-headers- silently failed to build these config files due to lack of packages flex and bison. sudo apt install flex bison sudo dpkg-reconfigure linux-headers- solved the problem, although the build still fails, but in a later stage. -- 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/1916517 Title: ERROR: Kernel configuration is invalid. include/generated/autoconf.h or include/config/auto.conf are missing. Status in linux package in Ubuntu: Confirmed Bug description: I'm unable to build dkms packages since it errors out with: make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/5.10.0-14-generic/build M=/var/lib/dkms/rtl88x2bu/git/build modules make[1]: Entering directory '/usr/src/linux-headers-5.10.0-14-generic' ERROR: Kernel configuration is invalid. include/generated/autoconf.h or include/config/auto.conf are missing. Run 'make oldconfig && make prepare' on kernel src to fix it. make[1]: *** [Makefile:745: include/config/auto.conf] Error 1 make[1]: Leaving directory '/usr/src/linux-headers-5.10.0-14-generic' make: *** [Makefile:2378: modules] Error 2 So I run: make oldconfig && make prepare in /usr/src/linux-headers-5.10.0-14-generic and it errors out with: make[1]: *** No rule to make target 'arch/x86/tools/relocs_32.c', needed by 'arch/x86/tools/relocs_32.o'. Stop. make: *** [arch/x86/Makefile:214: archscripts] Error 2 Thanks for your help! ProblemType: Bug DistroRelease: Ubuntu 21.04 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shemgp 6098 F pulseaudio /dev/snd/controlC1: shemgp 6098 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 23 00:59:55 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2015-09-28 (1974 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 34361A0 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=da81a856-84d5-4ca7-8c0a-4f20006730bc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.194 SourcePackage: linux StagingDrivers: ashmem_linux UpgradeStatus: Upgraded to hirsute on 2021-02-16 (6 days ago) dmi.bios.date: 09/25/2019 dmi.bios.release: 2.75 dmi.bios.vendor: LENOVO dmi.bios.version: GCETB5WW (2.75 ) dmi.board.asset.tag: Not Available dmi.board.name: 34361A0 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: Not Available dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrGCETB5WW(2.75):bd09/25/2019:br2.75:efr1.15:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X220 dmi.product.name: 34361A0 dmi.product.sku: LENOVO_MT_3436 dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929147] Re: fix system hang with 5.10 kernel + RX540 on RKL platform
** Tags removed: verification-done-hirsute ** Tags added: verification-needed-hirsute -- 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/1929147 Title: fix system hang with 5.10 kernel + RX540 on RKL platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: Fix Committed Bug description: [Impact] On RKL platform with AMD RX540, system would hang during boot-up. [Fix] AMD introduce a brand new firmware, polaris 12 MC firmware. This fix the issue and the system wouldn't hang during boot-up with AMD RX540. [Test] Verified on RKL platform and AMD RX540 System would boot-up and login to desktop successfully. [Where problems could occur] This's a brand new firmware to support Polaris-series, it may introduce new issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881421] Re: Thinkpad T440s trackpad and trackpoint stop working after resume from suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libinput (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/1881421 Title: Thinkpad T440s trackpad and trackpoint stop working after resume from suspend Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, this is a sporadic issue that sometimes appears, sometimes not. Usually once it starts happening it occurs on every suspend/resume cycle until the system is rebooted. The trackpad and the red trackpoint nub stop working after resume. This is on a Thinkpad T440s laptop currently running a fresh install of Ubuntu 20.04 with Gnome and no major modifications. Usually the trackpad can be fixed by unloading/loading the `psmouse` module. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libinput10 1.15.5-1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sat May 30 11:39:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20AR006RUS ProcEnviron: LANGUAGE=es_EC:es TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-33-generic root=UUID=9ed61bc7-d832-4808-908a-05704b574781 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: GJETA4WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AR006RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJETA4WW(2.54):bd03/27/2020:svnLENOVO:pn20AR006RUS:pvrThinkPadT440s:rvnLENOVO:rn20AR006RUS:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AR006RUS dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1881421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929147] Re: fix system hang with 5.10 kernel + RX540 on RKL platform
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1929147 Title: fix system hang with 5.10 kernel + RX540 on RKL platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: Fix Committed Bug description: [Impact] On RKL platform with AMD RX540, system would hang during boot-up. [Fix] AMD introduce a brand new firmware, polaris 12 MC firmware. This fix the issue and the system wouldn't hang during boot-up with AMD RX540. [Test] Verified on RKL platform and AMD RX540 System would boot-up and login to desktop successfully. [Where problems could occur] This's a brand new firmware to support Polaris-series, it may introduce new issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930868] Re: Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firm
"The sof-firmware is missing/buggy since 20.10, so everybody with a 2020 DELL XPS/Precision laptop has not being able to get any input/output audio since months already". Do you have bug link for those issues? I doubt it is not the sof- firmware's problem, maybe they are soundwire audio machines, need to upgrade the kernel. BTW, the sof-firmware in the ubuntu linux-firmware is also from sof-bin v1.6. ** Changed in: firmware-sof (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-firmware (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: firmware-sof (Ubuntu) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => High ** Changed in: firmware-sof (Ubuntu) Status: New => Triaged ** Changed in: linux-firmware (Ubuntu) Status: New => Triaged -- 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/1930868 Title: Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 Status in firmware-sof package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Triaged Bug description: (Reading database ... 220533 files and directories currently installed.) Preparing to unpack .../firmware-sof-signed_1.6.1-2_all.deb ... Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb Is there a work around? ProblemType: Package DistroRelease: Ubuntu 21.04 Package: firmware-sof-signed (not installed) ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 AptOrdering: firmware-sof-signed:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 4 17:22:54 2021 DpkgTerminalLog: Preparing to unpack .../firmware-sof-signed_1.6.1-2_all.deb ... Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 DuplicateSignature: package:firmware-sof-signed:(not installed) Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 ErrorMessage: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 InstallationDate: Installed on 2021-06-02 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: firmware-sof Title: package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1930868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931214] [NEW] touchpad is not working
Public bug reported: cursor is getting stuck ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-74-generic 5.4.0-74.83 ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pavan 3937 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 8 11:52:33 2021 InstallationDate: Installed on 2020-09-13 (268 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic root=UUID=f0e1642c-814b-4b45-87a2-da90c086640f ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-74-generic N/A linux-backports-modules-5.4.0-74-generic N/A linux-firmware1.187.12 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-09-30 (251 days ago) dmi.bios.date: 03/15/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A7 dmi.board.vendor: HP dmi.board.version: 80.41 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.18:bd03/15/2019:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A7:rvr80.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 4TT02PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931214 Title: touchpad is not working Status in linux package in Ubuntu: New Bug description: cursor is getting stuck ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-74-generic 5.4.0-74.83 ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pavan 3937 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 8 11:52:33 2021 InstallationDate: Installed on 2020-09-13 (268 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic root=UUID=f0e1642c-814b-4b45-87a2-da90c086640f ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-74-generic N/A linux-backports-modules-5.4.0-74-generic N/A linux-firmware1.187.12 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-09-30 (251 days ago) dmi.bios.date: 03/15/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A7 dmi.board.vendor: HP dmi.board.version: 80.41 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.18:bd03/15/2019:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A7:rvr80.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 4TT02PA#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/1931214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889110] Re: zfs pool locks and see "INFO: task txg_sync:4307 blocked for more than 120 seconds. "
I would say this is still an open issue. There is a long discussion on github about it and seems like there's currently no solution (yet?) https://github.com/openzfs/zfs/issues/9130 ** Bug watch added: github.com/openzfs/zfs/issues #9130 https://github.com/openzfs/zfs/issues/9130 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1889110 Title: zfs pool locks and see "INFO: task txg_sync:4307 blocked for more than 120 seconds. " Status in zfs-linux package in Ubuntu: Incomplete Bug description: ZFS filesystem becomes unresponsive and subsequent NFS shares unresponsive. ESXi sees all paths down. See this error 3 times in a row. [184383.479511] INFO: task txg_sync:4307 blocked for more than 120 seconds. [184383.479565] Tainted: P IO 5.4.0-42-generic #46-Ubuntu [184383.479607] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [184383.479655] txg_syncD0 4307 2 0x80004000 [184383.479658] Call Trace: [184383.479670] __schedule+0x2e3/0x740 [184383.479673] schedule+0x42/0xb0 [184383.479676] schedule_timeout+0x152/0x2f0 [184383.479683] ? __next_timer_interrupt+0xe0/0xe0 [184383.479685] io_schedule_timeout+0x1e/0x50 [184383.479697] __cv_timedwait_common+0x15e/0x1c0 [spl] [184383.479702] ? wait_woken+0x80/0x80 [184383.479710] __cv_timedwait_io+0x19/0x20 [spl] [184383.479816] zio_wait+0x11b/0x230 [zfs] [184383.479905] ? __raw_spin_unlock+0x9/0x10 [zfs] [184383.479983] dsl_pool_sync+0xbc/0x410 [zfs] [184383.480069] spa_sync_iterate_to_convergence+0xe0/0x1c0 [zfs] [184383.480156] spa_sync+0x312/0x5b0 [zfs] [184383.480245] txg_sync_thread+0x27a/0x310 [zfs] [184383.480334] ? txg_dispatch_callbacks+0x100/0x100 [zfs]
[Kernel-packages] [Bug 1930868] Re: Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firm
Couldn't we just use 1.6 to do the same now? I read that 1.6 worked for who got it compiled/installed in some way. The sof-firmware is missing/buggy since 20.10, so everybody with a 2020 DELL XPS/Precision laptop has not being able to get any input/output audio since months already. Is there a way to get it installed manually now? -- 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/1930868 Title: Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 Status in firmware-sof package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: (Reading database ... 220533 files and directories currently installed.) Preparing to unpack .../firmware-sof-signed_1.6.1-2_all.deb ... Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb Is there a work around? ProblemType: Package DistroRelease: Ubuntu 21.04 Package: firmware-sof-signed (not installed) ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 AptOrdering: firmware-sof-signed:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 4 17:22:54 2021 DpkgTerminalLog: Preparing to unpack .../firmware-sof-signed_1.6.1-2_all.deb ... Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 DuplicateSignature: package:firmware-sof-signed:(not installed) Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 ErrorMessage: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 InstallationDate: Installed on 2021-06-02 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: firmware-sof Title: package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1930868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929147] Re: fix system hang with 5.10 kernel + RX540 on RKL platform
For Focal, Verified on linux-firmware, 1.187.14, Plug RX540 gpu on RKL machine, connect monitor with DisplayPort. Boot up the machine Expected: System would boot-up and login to desktop successfully. Actual: System boot-up and login to desktop successfully. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1929147 Title: fix system hang with 5.10 kernel + RX540 on RKL platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: Fix Committed Bug description: [Impact] On RKL platform with AMD RX540, system would hang during boot-up. [Fix] AMD introduce a brand new firmware, polaris 12 MC firmware. This fix the issue and the system wouldn't hang during boot-up with AMD RX540. [Test] Verified on RKL platform and AMD RX540 System would boot-up and login to desktop successfully. [Where problems could occur] This's a brand new firmware to support Polaris-series, it may introduce new issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926236] Re: Fix The sound has noise while audio volume is maximum
Verified on linux-firmware, 1.187.14, With wx3200 gpu, connect monitor with DisplayPort and headset/speaker on the monitor. go to the sound page in the settings, turn the sound volume to maximum and press test button or play music. Expected: No noise when the music/audio is played. Actual: No noise. -- 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/1926236 Title: Fix The sound has noise while audio volume is maximum Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] The sound has noise while turning the audio volume to maximum [Fix] For VEGA & Polaris, need two patches(landed on mainline kernel) to fix and a modprobe 1.(50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 2.(9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on oem kernel 3. #modprobe amdgpu ppfeaturemask=0xfff7bffb. For Navi_1x, need smc firmware to fix. 1. (4fe6e53b96 linux-firmware) amdgpu: update navi10 SMC firmware 1. (8ab7abaf63 linux-firmware) amdgpu: update navi14 SMC firmware [Test] Verified on RKL platform A. with wx3200(Polaris series) and the following configuration 1. With these two patch, 1.1. (50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 1.2. (9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on oem kernel 2. doesn't append ppfeaturemask=0xfff7bffb Can't observe issue. B. With wx5500(Navi series) and update the related firmware, Can't observe issue [Where problems could occur] Because disabling DPM, the power consumption would be slightly higher. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926236] Re: Fix The sound has noise while audio volume is maximum
Verified on linux-firmware, 1.187.14, With wx3200 gpu, go to the sound page in the settings, turn the sound volume to maximum and press test button or play music. Expected: No noise when the music/audio is played. Actual: No noise. -- 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/1926236 Title: Fix The sound has noise while audio volume is maximum Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] The sound has noise while turning the audio volume to maximum [Fix] For VEGA & Polaris, need two patches(landed on mainline kernel) to fix and a modprobe 1.(50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 2.(9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on oem kernel 3. #modprobe amdgpu ppfeaturemask=0xfff7bffb. For Navi_1x, need smc firmware to fix. 1. (4fe6e53b96 linux-firmware) amdgpu: update navi10 SMC firmware 1. (8ab7abaf63 linux-firmware) amdgpu: update navi14 SMC firmware [Test] Verified on RKL platform A. with wx3200(Polaris series) and the following configuration 1. With these two patch, 1.1. (50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 1.2. (9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on oem kernel 2. doesn't append ppfeaturemask=0xfff7bffb Can't observe issue. B. With wx5500(Navi series) and update the related firmware, Can't observe issue [Where problems could occur] Because disabling DPM, the power consumption would be slightly higher. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829979] Re: memcg_max_usage_in_bytes from controllers test suite in LTP failed
It's a duplicate of lp:1897560. From comments there: - Observed in F/KVM, cycle sru-20210510. - Observed in B/KVM, cycle sru-20210510. - Observed in H/KVM, cycle sru-20210510. - Issue observed in F/KVM, cycle sru-20210412. - Also seen in bionic linux-fips 4.15.0-1057.65 for sru-20210315 - Also seen in bionic linux-gcp-fips 4.15.0-2007.8 for sru-20210315 (sru-20210222 as well) - found on bionic/ibm-gt 4.15.0-1084.93 - Found on Groovy lowlatency 5.8.0-31.33 ** This bug is no longer a duplicate of bug 1829984 memcg_usage_in_bytes from controllers test suite in LTP failed ** Tags added: 5.11 5.8 fips gcp gcp-fips groovy hirsute hwe hwe-5.4 kvm sru-20201109 sru-20210104 sru-20210125 sru-20210315 sru-20210412 sru-20210510 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829979 Title: memcg_max_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Bug description: startup='Wed May 22 05:58:50 2019' memcg_max_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_max_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 1 TINFO: Warming up pid: 30821 memcg_max_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 30821 memcg_max_usage_in_bytes_test 1 TFAIL: memory.max_usage_in_bytes is 4325376, 4194304 expected memcg_max_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TCONF: mem+swap is not enabled memcg_max_usage_in_bytes_test 2 TINFO: Starting test 3 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 2 TINFO: Warming up pid: 30855 memcg_max_usage_in_bytes_test 2 TINFO: Process is still here after warm up: 30855 memcg_max_usage_in_bytes_test 2 TFAIL: memory.max_usage_in_bytes is 4329472, 4194304 expected memcg_max_usage_in_bytes_test 3 TFAIL: memory.max_usage_in_bytes is 8192, 0 expected memcg_max_usage_in_bytes_test 4 TINFO: Starting test 4 sh: echo: I/O error memcg_max_usage_in_bytes_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 4 TCONF: mem+swap is not enabled tag=memcg_max_usage_in_bytes stime=1558504730 dur=3 exit=exited stat=33 core=no cu=8 cs=7 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 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: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:06:31 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys
