[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
This bug is related to https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1928244 https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1912811 Kernel 5.13 can be compiled in one of the two ways: 1. Use dwarves 1.21, which needs Ubuntu 21.04 and breaks installation for older systems 2. Disable CONFIG_DEBUG_INFO_BTF, thus allowing it to be compiled with older toolchains and thus, for older Ubuntu releases. I believe the sensible approach would be to temporarily follow the second option until a better solution is found as proposed in 1912811. -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916919] Re: after upgrade to 5.4.0-66 monitor remains black after off/on cycle
As a workaround you can try booting with "amdgpu.dc=0" Although I don't know if Vega supports disabling DC. With DC disabled, the GPU cannot know if your monitor has been turned off. Another possible solution is to use an SSH session to try to restore your monitor, typing: DISPLAY=:0.0 xrandr --auto -- 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/1916919 Title: after upgrade to 5.4.0-66 monitor remains black after off/on cycle Status in linux package in Ubuntu: Incomplete Bug description: i updated today to linux kernel 5.4.0-66-generic. since then the monitor (HDMI) remains black when switched off and on again. this can be corrected once, if a virtual text console hasn't been used so far by switching to a virtual text console and then back to the desktop. Ubuntu 5.4.0-66.74-generic 5.4.86 (Linux Mint 20, Cinnamon 4.6.7) lspci-vnvn.log attached Asrock DeskMini A300 AMD Ryzen 5 2400G with Radeon Vega Graphics × 4 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later
I can also confirm 5.3.0-59 fixed the bug on my HW as well. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-meta-hwe (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/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later Status in DRI: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-meta-hwe package in Ubuntu: Fix Released Bug description: When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or later (including 5.3.0-53), everything seems to be working as usual. However, when I shutdown, the system will only soft shutdown, with the CPU still running at full power, forcing me to hold down the power button to fully power off affected systems. If I reboot, it will cause the system to hang and not respond. Either way, a hard reset or poweroff will be required, and this is not an option for systems being remotely accessed. It is not possible for me to collect kernel logs at this point, unless something wrong is happening in those kernel versions before the actual shutdown. It is possible that this may also occur on Ubuntu 20.04 with kernel versions 5.4.0-29 and later, but I have not yet tested this out. This problem is occurring on both my desktop and laptop computers which respectively are: * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU In the meantime, I am stuck on kernel version 5.3.0-51, as that is the last working 5.3.x kernel version offered in the standard Ubuntu repositories that doesn't have this problem, without me having to use PPAs. I don't know if this problem also occurs on systems with Intel CPUs, as I don't own any recently-made system (last 3 years from 2017) with such CPUs to test if this problem occurs on them. To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881494] Re: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
Hi, I'm just passing by. Regarding amdgpu issues related with Ryzen / Vega iGPU, there are a couple steps you can try: 1. Try a newer firmware blob. Download e.g. 1a. Download the latest firmware and unpack it https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20200519.tar.gz 1b. Backup your /lib/firmware folder 1c. sudo make install A newer firmware could fix the issue (it did for me on Ubuntu 18.04). If this fixes your problem, remember to freeze the linux-firmware package otherwise the next update will overwrite your changes and instability will come back. 2. Try a newer libdrm. Kernel updates for amdgpu go hand in hand with libdrm, but sometimes backports get these out of sync, or you try a mainline kernel but without a mainline libdrm. Download latest libdrm from https://gitlab.freedesktop.org/mesa/drm compile it and replace your Ubuntu's installation with your custom build one -- 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/1881494 Title: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: suspend to ram crashes amdgpu. System is still accessible via SSH after resume from standby. Happens when X is running (gdm/gnome with 3d acceleration) and also when X is stopped. Also the computer never really goes into standby. The cpu fan is running all the time and the power button is fully lighted up. Nevertheless, I need to press CTRL to "wake" it, so I can access it via SSH. I'll attach the dmesg output of several attempts. This is the hardware: https://store.hp.com/GermanyStore/Merch/Product.aspx?id=9YN58EA=ABD=NTB Tested EFI and BIOS bootmode. Please let me know if I can help tracking this down. I'm a software developer (sadly not a kernel developer), so you can ask dirty technical questions ;-) Workaround: Enable hibernation (suspend to disk) and use instead of suspend to ram (standby). What didn't help: Kernel parameters: no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush echo mem > /sys/power/state systemctl start suspend.target echo 0 > /sys/power/pm_async Upgrading kernel from 5.4 to: 5.6.0-1010-oem Using the kernel parameters no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush and doing echo mem > /sys/power/state before suspend made the system acutally not crash. Nevertheless, the cpu fan and the power button stay full on/lighted. So the system doesn't really go to standby either. I'll try to find the minimal combination of kernel parameters. nomodeset seems to be essential, but not sufficient. Without nomodeset the system wakes again for a few seconds, but freezes a moment later (ssh still accessible). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 18:43:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ar0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1010-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.vendor: AMI dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 85DE dmi.board.vendor: HP dmi.board.version: 41.36 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.19:bd12/26/2019:svnHP:pnHPENVYx360Convertible13-ar0xxx:pvr:rvnHP:rn85DE:rvr41.36:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name:
[Kernel-packages] [Bug 1879807] Re: 5.3.0-53 Kernel system falis to reboot after install
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- 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/1879807 Title: 5.3.0-53 Kernel system falis to reboot after install Status in linux package in Ubuntu: Confirmed Bug description: I cant post the requested terminal outputs because I can't install the kernel, but here is the system information: System:Host: LM Kernel: 5.3.0-51-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Desktop Mobo: ASRock model: A300M-STX serial: UEFI: American Megatrends v: P3.60 date: 10/28/2019 Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: charge: 55% status: Discharging CPU: Topology: Quad Core model: AMD Ryzen 3 3200G with Radeon Vega Graphics bits: 64 type: MCP arch: Zen rev: 1 L2 cache: 2048 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 28803 Speed: 1600 MHz min/max: 1400/3600 MHz Core speeds (MHz): 1: 1600 2: 1600 3: 4000 4: 1600 Graphics: Device-1: AMD Picasso driver: amdgpu v: kernel bus ID: 04:00.0 chip ID: 1002:15d8 Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD RAVEN (DRM 3.33.0 5.3.0-51-generic LLVM 9.0.0) v: 4.5 Mesa 19.2.8 direct render: Yes Audio: Device-1: AMD driver: snd_hda_intel v: kernel bus ID: 04:00.1 chip ID: 1002:15de Device-2: AMD vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 04:00.6 chip ID: 1022:15e3 Sound Server: ALSA v: k5.3.0-51-generic Network: Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel bus ID: 02:00.0 chip ID: 8086:24fb IF: wlp2s0 state: down mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169 v: kernel port: f000 bus ID: 03:00.0 chip ID: 10ec:8168 IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: Drives:Local Storage: total: 350.27 GiB used: 18.08 GiB (5.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: RD400 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: ID-2: /dev/sda vendor: Crucial model: CT120BX500SSD1 size: 111.79 GiB speed: 6.0 Gb/s serial: temp: 39 C Partition: ID-1: / size: 233.26 GiB used: 10.51 GiB (4.5%) fs: ext4 dev: /dev/nvme0n1p2 USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 1d6b:0002 Hub: 1-3:2 info: Genesys Logic Hub ports: 4 rev: 2.0 chip ID: 05e3:0608 Device-1: 1-3.1:3 info: Intel type: Bluetooth driver: btusb rev: 2.0 chip ID: 8087:0aa7 Hub: 1-3.2:4 info: Genesys Logic Hub ports: 4 rev: 2.0 chip ID: 05e3:0608 Device-2: 1-3.2.2:5 info: Logitech Illuminated Keyboard type: Keyboard,Mouse driver: hid-generic,usbhid rev: 2.0 chip ID: 046d:c318 Device-3: 1-3.2.3:6 info: Logitech Unifying Receiver type: Mouse,HID driver: logitech-djreceiver,usbhid rev: 2.0 chip ID: 046d:c52f Hub: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 chip ID: 1d6b:0003 Hub: 3-0:1 info: Full speed (or root) Hub ports: 1 rev: 2.0 chip ID: 1d6b:0002 Hub: 4-0:1 info: Full speed (or root) Hub ports: 1 rev: 3.1 chip ID: 1d6b:0003 Sensors: System Temperatures: cpu: 38.5 C mobo: N/A Fan Speeds (RPM): N/A Repos: No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 1: deb [arch=amd64] http: //dl.google.com/linux/earth/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //mirror.clarkson.edu/linuxmint/packages tricia main upstream import backport 2: deb http: //archive.linux.duke.edu/ubuntu bionic main restricted universe multiverse 3: deb http: //archive.linux.duke.edu/ubuntu bionic-updates main restricted universe multiverse 4: deb http: //archive.linux.duke.edu/ubuntu bionic-backports main restricted
[Kernel-packages] [Bug 1880005] Re: Shutdown/Poweroff Failed with Kernel 5.0.3-53
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug is no longer a duplicate of bug 1879807 5.3.0-53 Kernel system falis to reboot after install ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- 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/1880005 Title: Shutdown/Poweroff Failed with Kernel 5.0.3-53 Status in linux package in Ubuntu: Incomplete Bug description: I have installed Linux Mint Mate 19.3 (Tricia, 64-bits). When I upgraded the Kernel to version 5.3.0-53, the on / off function failed, the screen is off but the laptop is still working, the light of manual shutdown button is still lit. There is no problem with the previous version of the kernel: 5.3.0-51. My laptop is Lenovo YOGA 530-14ARR with precessor AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx × 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879997] Re: HP-255-G7-Notebook-PC 5.3.0-51-generic
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug is no longer a duplicate of bug 1879807 5.3.0-53 Kernel system falis to reboot after install ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- 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/1879997 Title: HP-255-G7-Notebook-PC 5.3.0-51-generic Status in linux package in Ubuntu: Incomplete Bug description: HP-255-G7-Notebook-PC System wont reboot or shutdown after kernel 5.3.0-53 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881253] Re: PC fails to power off at end of shutdown
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug is no longer a duplicate of bug 1879807 5.3.0-53 Kernel system falis to reboot after install ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- 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/1881253 Title: PC fails to power off at end of shutdown Status in linux package in Ubuntu: Confirmed Bug description: Installed Kernel 5.3.0-53 on PC running Linux Mint 19.3. When shutting down the computer seems to do this as per normal but when the screen goes blank at the end of shutdown but the computer stays powered up - LED on, fans running but screens are blank, keyboard (REISUB) has no effect. The only way to recover the situation is to hold the power button until the pc switches off. Shutdown worked normally and pc powered off with previous kernel 5.3.0-51. cat /proc/version_signature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 lsb_release -rd Description: Linux Mint 19.3 Tricia Release: 19.3 lspci-vnvn.log attached --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mark 1529 F pulseaudio /dev/snd/controlC1: mark 1529 F pulseaudio /dev/snd/controlC0: mark 1529 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 InstallationDate: Installed on 2020-03-09 (80 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp37s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A38 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=8b323ba9-b13a-40c8-a2f7-52f53a14018a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.173.18 RfKill: Tags: tricia Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 11/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M PRO-VDH MAX (MS-7A38) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 8.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 8.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB.40:bd11/07/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr8.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-VDHMAX(MS-7A38):rvr8.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr8.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A38 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 8.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880119] Re: System hangs on shut down Kernel 5.3.0-53
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug is no longer a duplicate of bug 1879807 5.3.0-53 Kernel system falis to reboot after install ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- 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/1880119 Title: System hangs on shut down Kernel 5.3.0-53 Status in linux package in Ubuntu: New Bug description: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 1676 F pulseaudio /dev/snd/controlC1: toni 1676 F pulseaudio /dev/snd/controlC0: toni 1676 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 InstallationDate: Installed on 2019-07-25 (301 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.173.18 RfKill: Tags: tricia Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M S2H 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:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874325] Re: Eoan update: upstream stable patchset 2020-04-22
This series of patches broke:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-
hwe/+bug/1880041/comments/19
Commit
drm/amdgpu: fix gfx hang during suspend with video playback (v2)
https://kernel.ubuntu.com/git/ubuntu/ubuntu-
bionic.git/commit/?id=6ad2b975986441870a9a67051f9571b5c09c2569
has a known issue and already has a fix in upstream:
https://gitlab.freedesktop.org/drm/amd/-/issues/1094
However this fix has not been backported to 18.04 LTS HWE, thus leaving
Ryzen systems with integrated GPUs unable to shutdown or reboot.
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1094
https://gitlab.freedesktop.org/drm/amd/-/issues/1094
--
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/1874325
Title:
Eoan update: upstream stable patchset 2020-04-22
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Fix Released
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:
upstream stable patchset 2020-04-22
Ported from the following upstream stable releases:
v4.19.116, v5.4.33
from git://git.kernel.org/
ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
net: vxge: fix wrong __VA_ARGS__ usage
hinic: fix a bug of waitting for IO stopped
hinic: fix wrong para of wait_for_completion_timeout
cxgb4/ptp: pass the sign of offset delta in FW CMD
qlcnic: Fix bad kzalloc null test
i2c: st: fix missing struct parameter description
cpufreq: imx6q: Fixes unwanted cpu overclocking on i.MX6ULL
media: venus: hfi_parser: Ignore HEVC encoding for V1
firmware: arm_sdei: fix double-lock on hibernate with shared events
null_blk: Fix the null_add_dev() error path
null_blk: Handle null_add_dev() failures properly
null_blk: fix spurious IO errors after failed past-wp access
xhci: bail out early if driver can't accress host in resume
x86: Don't let pgprot_modify() change the page encryption bit
block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
irqchip/versatile-fpga: Handle chained IRQs properly
sched: Avoid scale real weight down to zero
selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
PCI/switchtec: Fix init_completion race condition with poll_wait()
media: i2c: video-i2c: fix build errors due to 'imply hwmon'
libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
pstore/platform: fix potential mem leak if pstore_init_fs failed
gfs2: Don't demote a glock until its revokes are written
x86/boot: Use unsigned comparison for addresses
efi/x86: Ignore the memory attributes table on i386
genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
block: Fix use-after-free issue accessing struct io_cq
media: i2c: ov5695: Fix power on and off sequences
usb: dwc3: core: add support for disabling SS instances in park mode
irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
md: check arrays is suspended in mddev_detach before call quiesce operations
firmware: fix a double abort case with fw_load_sysfs_fallback
locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
block, bfq: fix use-after-free in bfq_idle_slice_timer_body
btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is at
least queued
btrfs: remove a BUG_ON() from merge_reloc_roots()
btrfs: track reloc roots based on their commit root bytenr
ASoC: fix regwmask
ASoC: dapm: connect virtual mux with default value
ASoC: dpcm: allow start or stop during pause for backend
ASoC: topology: use name_prefix for new kcontrol
usb: gadget: f_fs: Fix use after free issue as part of queue failure
usb: gadget: composite: Inform controller driver of self-powered
ALSA: usb-audio: Add mixer workaround for TRX40 and co
ALSA: hda: Add driver blacklist
ALSA: hda: Fix potential access overflow in beep helper
ALSA: ice1724: Fix invalid access for enumerated ctl items
ALSA: pcm: oss: Fix regression by buffer overflow fix
ALSA: doc: Document PC Beep Hidden Register on Realtek ALC256
ALSA: hda/realtek - Set principled PC Beep configuration for ALC256
ALSA: hda/realtek - Remove now-unnecessary XPS 13 headphone noise fixups
ALSA: hda/realtek - Add quirk for MSI GL63
media: ti-vpe: cal: fix disable_irqs to only the intended target
acpi/x86: ignore unspecified bit
[Kernel-packages] [Bug 1879185] Re: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- 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/1879185 Title: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx Status in linux package in Ubuntu: Confirmed Bug description: I reset the previous kernel to be able to post, because it is very difficult to work like this, this happens randomly, intermittently with each application or without having anything open. It happened from the last update to kernel 5.3, I suppose that it is the very new laptop since in another partition I have Kali and it happens the same. I appreciate your help, I list the characteristics of this laptop :roll: ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ inxi -Fxz System: Host: ydhm-HP-Laptop-14-cm0xxx Kernel: 5.0.0-32-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Xfce 4.14.1 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: HP product: HP Laptop 14-cm0xxx v: N/A serial: Mobo: HP model: 84A2 v: 84.24 serial: UEFI: AMI v: F.42 date: 07/03/2019 Battery: ID-1: BAT0 charge: 28.9 Wh condition: 40.8/40.8 Wh (100%) model: Hewlett-Packard Primary status: Charging CPU: Topology: Dual Core model: AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 19962 Speed: 1433 MHz min/max: 1600/2500 MHz Core speeds (MHz): 1: 1400 2: 1398 3: 1490 4: 1441 Graphics: Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 04:00.0 Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz OpenGL: renderer: AMD RAVEN (DRM 3.27.0 5.0.0-32-generic LLVM 9.0.0) v: 4.5 Mesa 19.2.8 direct render: Yes Audio: Device-1: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.1 Device-2: AMD vendor: Hewlett-Packard driver: N/A bus ID: 04:00.5 Device-3: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.6 Sound Server: ALSA v: k5.0.0-32-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: f000 bus ID: 02:00.0 IF: eno1 state: down mac: Device-2: Realtek vendor: Hewlett-Packard driver: N/A port: e000 bus ID: 03:00.0 Device-3: D-Link DWA-125 Wireless N 150 Adapter(rev.A3) [Ralink RT5370] type: USB driver: rt2800usb bus ID: 1-3:3 IF: wlxacf1df084ac8 state: up mac: Drives: Local Storage: total: 931.51 GiB used: 23.91 GiB (2.6%) ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS541010B7E610 size: 931.51 GiB Partition: ID-1: / size: 139.20 GiB used: 21.62 GiB (15.5%) fs: ext4 dev: /dev/sda5 Sensors: System Temperatures: cpu: 45.1 C mobo: N/A gpu: amdgpu temp: 45 C Fan Speeds (RPM): N/A Info: Processes: 199 Uptime: 27m Memory: 3.38 GiB used: 1.18 GiB (35.0%) Init: systemd runlevel: 5 Compilers: gcc: 7.5.0 Shell: bash v: 4.4.20 inxi: 3.0.32 / ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ rfkill list all 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no / ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ mokutil --sb-state SecureBoot disabled Platform is in Setup Mode Ps: I also don't have wifi and bluetooth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880381] Re: No full shutdown 5.3.0-53
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- 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/1880381 Title: No full shutdown 5.3.0-53 Status in linux package in Ubuntu: Confirmed Bug description: After shutdown the fan is still running. I need to push the power-button to final shutdown. So I changed back to 5.3.0-51 and blocked update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880695] Re: system hangs at shutdown or restart
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 ** This bug has been marked a duplicate of bug 1880041 Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later -- 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/1880695 Title: system hangs at shutdown or restart Status in linux package in Ubuntu: Confirmed Bug description: Release: Linux Mint 19.3 Tricia What you expected to happen: The OS is shut down and the computer is powered off when the shutdown button is clicked. 4) What happened instead System hangs at a screen with logo or no screen signal after shutdown or reboot is commanded (via button or command line). The OS has no response, the computer is still on power as normal. This issue occurs after a kernel update from 4.15.0 to 5.3.0.51 and keeps up to current kernel 5.3.0.53. version: Linux version 5.3.0-53-generic (buildd@lgw01-amd64-016) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #47~18.04.1-Ubuntu SMP Thu May 7 13:10:50 UTC 2020 pci: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex [1022:1450] Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex [1022:1450] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 59) Subsystem: Gigabyte Technology Co., Ltd FCH SMBus Controller [1458:5001] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: nvme Kernel modules: nvme 02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:43b9] (rev 02) (prog-if 30 [XHCI]) Subsystem: ASMedia Technology Inc. Device [1b21:1142] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF-
[Kernel-packages] [Bug 1880695] Re: system hangs at shutdown or restart
Duplicate of https://bugs.launchpad.net/ubuntu/+source/linux-meta- hwe/+bug/1880041 Please pass there by and select that you're affected too so it gets more attention. -- 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/1880695 Title: system hangs at shutdown or restart Status in linux package in Ubuntu: Confirmed Bug description: Release: Linux Mint 19.3 Tricia What you expected to happen: The OS is shut down and the computer is powered off when the shutdown button is clicked. 4) What happened instead System hangs at a screen with logo or no screen signal after shutdown or reboot is commanded (via button or command line). The OS has no response, the computer is still on power as normal. This issue occurs after a kernel update from 4.15.0 to 5.3.0.51 and keeps up to current kernel 5.3.0.53. version: Linux version 5.3.0-53-generic (buildd@lgw01-amd64-016) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #47~18.04.1-Ubuntu SMP Thu May 7 13:10:50 UTC 2020 pci: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex [1022:1450] Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex [1022:1450] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 59) Subsystem: Gigabyte Technology Co., Ltd FCH SMBus Controller [1458:5001] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: nvme Kernel modules: nvme 02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:43b9] (rev 02) (prog-if 30 [XHCI]) Subsystem: ASMedia Technology Inc. Device [1b21:1142] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: xhci_hcd
[Kernel-packages] [Bug 1879807] Re: 5.3.0-53 Kernel system falis to reboot after install
Duplicate tickets: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1880425 https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 Possibly duplicate (unsure): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879185 -- 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/1879807 Title: 5.3.0-53 Kernel system falis to reboot after install Status in linux package in Ubuntu: Confirmed Bug description: I cant post the requested terminal outputs because I can't install the kernel, but here is the system information: System:Host: LM Kernel: 5.3.0-51-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Desktop Mobo: ASRock model: A300M-STX serial: UEFI: American Megatrends v: P3.60 date: 10/28/2019 Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: charge: 55% status: Discharging CPU: Topology: Quad Core model: AMD Ryzen 3 3200G with Radeon Vega Graphics bits: 64 type: MCP arch: Zen rev: 1 L2 cache: 2048 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 28803 Speed: 1600 MHz min/max: 1400/3600 MHz Core speeds (MHz): 1: 1600 2: 1600 3: 4000 4: 1600 Graphics: Device-1: AMD Picasso driver: amdgpu v: kernel bus ID: 04:00.0 chip ID: 1002:15d8 Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD RAVEN (DRM 3.33.0 5.3.0-51-generic LLVM 9.0.0) v: 4.5 Mesa 19.2.8 direct render: Yes Audio: Device-1: AMD driver: snd_hda_intel v: kernel bus ID: 04:00.1 chip ID: 1002:15de Device-2: AMD vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 04:00.6 chip ID: 1022:15e3 Sound Server: ALSA v: k5.3.0-51-generic Network: Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel bus ID: 02:00.0 chip ID: 8086:24fb IF: wlp2s0 state: down mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169 v: kernel port: f000 bus ID: 03:00.0 chip ID: 10ec:8168 IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: Drives:Local Storage: total: 350.27 GiB used: 18.08 GiB (5.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: RD400 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: ID-2: /dev/sda vendor: Crucial model: CT120BX500SSD1 size: 111.79 GiB speed: 6.0 Gb/s serial: temp: 39 C Partition: ID-1: / size: 233.26 GiB used: 10.51 GiB (4.5%) fs: ext4 dev: /dev/nvme0n1p2 USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 1d6b:0002 Hub: 1-3:2 info: Genesys Logic Hub ports: 4 rev: 2.0 chip ID: 05e3:0608 Device-1: 1-3.1:3 info: Intel type: Bluetooth driver: btusb rev: 2.0 chip ID: 8087:0aa7 Hub: 1-3.2:4 info: Genesys Logic Hub ports: 4 rev: 2.0 chip ID: 05e3:0608 Device-2: 1-3.2.2:5 info: Logitech Illuminated Keyboard type: Keyboard,Mouse driver: hid-generic,usbhid rev: 2.0 chip ID: 046d:c318 Device-3: 1-3.2.3:6 info: Logitech Unifying Receiver type: Mouse,HID driver: logitech-djreceiver,usbhid rev: 2.0 chip ID: 046d:c52f Hub: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 chip ID: 1d6b:0003 Hub: 3-0:1 info: Full speed (or root) Hub ports: 1 rev: 2.0 chip ID: 1d6b:0002 Hub: 4-0:1 info: Full speed (or root) Hub ports: 1 rev: 3.1 chip ID: 1d6b:0003 Sensors: System Temperatures: cpu: 38.5 C mobo: N/A Fan Speeds (RPM): N/A Repos: No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 1: deb [arch=amd64] http: //dl.google.com/linux/earth/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //mirror.clarkson.edu/linuxmint/packages tricia main upstream import backport 2: deb http: //archive.linux.duke.edu/ubuntu bionic main restricted universe multiverse 3: deb http: //archive.linux.duke.edu/ubuntu bionic-updates main restricted universe multiverse 4: deb http: //archive.linux.duke.edu/ubuntu bionic-backports main restricted
[Kernel-packages] [Bug 1852857] Re: Use more modern Raven Ridge firmware in linux-firmware package
You mean bisecting the git commits from mainline linux-firmware; compare it against https://kernel.ubuntu.com/git/ubuntu/linux- firmware.git/log/?h=bionic until I isolate the culprit(s)? Yes I can do that. It will take a while though (laptop needs to reboot with every attempt, it may take a while to crash, etc) Does anyone know if: service lightdm stop rmmod amdgpu modprobe amdgpu service lightdm start will reupload the firmware blob? That would speed up the testing process tremendously. -- 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/1852857 Title: Use more modern Raven Ridge firmware in linux-firmware package Status in linux-firmware package in Ubuntu: New Bug description: I own a: CPU: AMD Ryzen 5 2500U GPU: AMD Raven Ridge (Vega 8) Laptop model: Lenovo IdeaPad 330S (330S-15ARR) Description: Ubuntu 18.04.3 LTS Release: 18.04 linux-firmware: Installed: 1.173.12 Candidate: 1.173.12 Version table: *** 1.173.12 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 100 /var/lib/dpkg/status 1.173 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages The firmware provided by Ubuntu 18.04 is too old and causes frequent system freezes, particularly when using the web browser. When it freezes, the mouse is the only thing that works, but the GPU gets completely locked up. Keyboard also gets locked up (even Num Lock doesn't respond). There are no crash reports automatically generated. The logs get corrupted so it's impossible to know what happened. Updating it to a new firmware version fixes all freezes and system stability becomes rock solid. I'm not sure which exactly is the relevant firmware file, but I'm using these: fe5ec673b44d95c686a240a8d138f499 raven2_asd.bin a671f876b7ea6ff9f93dc56e0e147157 raven2_ce.bin be6c5c565ec341ee69f6d99a0ecb109d raven2_gpu_info.bin 5d7b9b404c424c692342cc1408553025 raven2_me.bin 81f2957c4512ec2595bb1dbdc37f52ca raven2_mec2.bin 81f2957c4512ec2595bb1dbdc37f52ca raven2_mec.bin 4d7651ab7fc4dba1abcfaf4a88f40686 raven2_pfp.bin 4ac07f88b9c4aa4fe026be87cb16ceda raven2_rlc.bin ac3a488f651921bc5a21b5a443ee7c23 raven2_sdma.bin 2372175130589c169afc4bc0e0435705 raven2_vcn.bin fe5ec673b44d95c686a240a8d138f499 raven_asd.bin 3e4aeb199a9e1c56a398d5b4ff6a7166 raven_ce.bin b5387b400b0ee4b04565a5179aebb9cd raven_dmcu.bin 052cdc264b228656dff12b95def55c54 raven_gpu_info.bin b16a081785f2f75a6f326ca5ca92113d raven_me.bin 4390c8485f4d4583ae878aa227968a48 raven_mec2.bin 4390c8485f4d4583ae878aa227968a48 raven_mec.bin f69ef2e297e66eb68eecb02540780f4c raven_pfp.bin 0e5fff019103b4cdc5a0366e29411fdd raven_rlc.bin df5f1ef96feade475a9c83451d840bb3 raven_sdma.bin 7e22527c2ef5e9b6e4e871d6ec546848 raven_vcn.bin There's the possibility that I'm wrong and the actually firmware file is not related to Raven Ridge (I doubt it, my usage when it freezes points to being a GPU problem) More specifically I'm using these https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tag/?h=20190815 I have been working with these new firmware files for months and no crashes. Yesterday linux-firmware was updated reverting my changes, and it started locking up again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1852857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852857] Re: Use more modern Raven Ridge firmware in linux-firmware package
** Attachment added: "uname.txt" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1852857/+attachment/5305900/+files/uname.txt -- 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/1852857 Title: Use more modern Raven Ridge firmware in linux-firmware package Status in linux-firmware package in Ubuntu: New Bug description: I own a: CPU: AMD Ryzen 5 2500U GPU: AMD Raven Ridge (Vega 8) Laptop model: Lenovo IdeaPad 330S (330S-15ARR) Description: Ubuntu 18.04.3 LTS Release: 18.04 linux-firmware: Installed: 1.173.12 Candidate: 1.173.12 Version table: *** 1.173.12 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 100 /var/lib/dpkg/status 1.173 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages The firmware provided by Ubuntu 18.04 is too old and causes frequent system freezes, particularly when using the web browser. When it freezes, the mouse is the only thing that works, but the GPU gets completely locked up. Keyboard also gets locked up (even Num Lock doesn't respond). There are no crash reports automatically generated. The logs get corrupted so it's impossible to know what happened. Updating it to a new firmware version fixes all freezes and system stability becomes rock solid. I'm not sure which exactly is the relevant firmware file, but I'm using these: fe5ec673b44d95c686a240a8d138f499 raven2_asd.bin a671f876b7ea6ff9f93dc56e0e147157 raven2_ce.bin be6c5c565ec341ee69f6d99a0ecb109d raven2_gpu_info.bin 5d7b9b404c424c692342cc1408553025 raven2_me.bin 81f2957c4512ec2595bb1dbdc37f52ca raven2_mec2.bin 81f2957c4512ec2595bb1dbdc37f52ca raven2_mec.bin 4d7651ab7fc4dba1abcfaf4a88f40686 raven2_pfp.bin 4ac07f88b9c4aa4fe026be87cb16ceda raven2_rlc.bin ac3a488f651921bc5a21b5a443ee7c23 raven2_sdma.bin 2372175130589c169afc4bc0e0435705 raven2_vcn.bin fe5ec673b44d95c686a240a8d138f499 raven_asd.bin 3e4aeb199a9e1c56a398d5b4ff6a7166 raven_ce.bin b5387b400b0ee4b04565a5179aebb9cd raven_dmcu.bin 052cdc264b228656dff12b95def55c54 raven_gpu_info.bin b16a081785f2f75a6f326ca5ca92113d raven_me.bin 4390c8485f4d4583ae878aa227968a48 raven_mec2.bin 4390c8485f4d4583ae878aa227968a48 raven_mec.bin f69ef2e297e66eb68eecb02540780f4c raven_pfp.bin 0e5fff019103b4cdc5a0366e29411fdd raven_rlc.bin df5f1ef96feade475a9c83451d840bb3 raven_sdma.bin 7e22527c2ef5e9b6e4e871d6ec546848 raven_vcn.bin There's the possibility that I'm wrong and the actually firmware file is not related to Raven Ridge (I doubt it, my usage when it freezes points to being a GPU problem) More specifically I'm using these https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tag/?h=20190815 I have been working with these new firmware files for months and no crashes. Yesterday linux-firmware was updated reverting my changes, and it started locking up again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1852857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852857] [NEW] Use more modern Raven Ridge firmware in linux-firmware package
Public bug reported: I own a: CPU: AMD Ryzen 5 2500U GPU: AMD Raven Ridge (Vega 8) Laptop model: Lenovo IdeaPad 330S (330S-15ARR) Description:Ubuntu 18.04.3 LTS Release:18.04 linux-firmware: Installed: 1.173.12 Candidate: 1.173.12 Version table: *** 1.173.12 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 100 /var/lib/dpkg/status 1.173 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages The firmware provided by Ubuntu 18.04 is too old and causes frequent system freezes, particularly when using the web browser. When it freezes, the mouse is the only thing that works, but the GPU gets completely locked up. Keyboard also gets locked up (even Num Lock doesn't respond). There are no crash reports automatically generated. The logs get corrupted so it's impossible to know what happened. Updating it to a new firmware version fixes all freezes and system stability becomes rock solid. I'm not sure which exactly is the relevant firmware file, but I'm using these: fe5ec673b44d95c686a240a8d138f499 raven2_asd.bin a671f876b7ea6ff9f93dc56e0e147157 raven2_ce.bin be6c5c565ec341ee69f6d99a0ecb109d raven2_gpu_info.bin 5d7b9b404c424c692342cc1408553025 raven2_me.bin 81f2957c4512ec2595bb1dbdc37f52ca raven2_mec2.bin 81f2957c4512ec2595bb1dbdc37f52ca raven2_mec.bin 4d7651ab7fc4dba1abcfaf4a88f40686 raven2_pfp.bin 4ac07f88b9c4aa4fe026be87cb16ceda raven2_rlc.bin ac3a488f651921bc5a21b5a443ee7c23 raven2_sdma.bin 2372175130589c169afc4bc0e0435705 raven2_vcn.bin fe5ec673b44d95c686a240a8d138f499 raven_asd.bin 3e4aeb199a9e1c56a398d5b4ff6a7166 raven_ce.bin b5387b400b0ee4b04565a5179aebb9cd raven_dmcu.bin 052cdc264b228656dff12b95def55c54 raven_gpu_info.bin b16a081785f2f75a6f326ca5ca92113d raven_me.bin 4390c8485f4d4583ae878aa227968a48 raven_mec2.bin 4390c8485f4d4583ae878aa227968a48 raven_mec.bin f69ef2e297e66eb68eecb02540780f4c raven_pfp.bin 0e5fff019103b4cdc5a0366e29411fdd raven_rlc.bin df5f1ef96feade475a9c83451d840bb3 raven_sdma.bin 7e22527c2ef5e9b6e4e871d6ec546848 raven_vcn.bin There's the possibility that I'm wrong and the actually firmware file is not related to Raven Ridge (I doubt it, my usage when it freezes points to being a GPU problem) More specifically I'm using these https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tag/?h=20190815 I have been working with these new firmware files for months and no crashes. Yesterday linux-firmware was updated reverting my changes, and it started locking up again. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci.txt" https://bugs.launchpad.net/bugs/1852857/+attachment/5305899/+files/lspci.txt -- 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/1852857 Title: Use more modern Raven Ridge firmware in linux-firmware package Status in linux-firmware package in Ubuntu: New Bug description: I own a: CPU: AMD Ryzen 5 2500U GPU: AMD Raven Ridge (Vega 8) Laptop model: Lenovo IdeaPad 330S (330S-15ARR) Description: Ubuntu 18.04.3 LTS Release: 18.04 linux-firmware: Installed: 1.173.12 Candidate: 1.173.12 Version table: *** 1.173.12 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 100 /var/lib/dpkg/status 1.173 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages The firmware provided by Ubuntu 18.04 is too old and causes frequent system freezes, particularly when using the web browser. When it freezes, the mouse is the only thing that works, but the GPU gets completely locked up. Keyboard also gets locked up (even Num Lock doesn't respond). There are no crash reports automatically generated. The logs get corrupted so it's impossible to know what happened. Updating it to a new firmware version fixes all freezes and system stability becomes rock solid. I'm not sure which exactly is the relevant firmware file, but I'm using these: fe5ec673b44d95c686a240a8d138f499 raven2_asd.bin a671f876b7ea6ff9f93dc56e0e147157 raven2_ce.bin be6c5c565ec341ee69f6d99a0ecb109d raven2_gpu_info.bin 5d7b9b404c424c692342cc1408553025 raven2_me.bin 81f2957c4512ec2595bb1dbdc37f52ca raven2_mec2.bin 81f2957c4512ec2595bb1dbdc37f52ca raven2_mec.bin
