Re: Linux Mint 20.04 5.11 issue
When launching Chromium from a terminal window, I get the following output: 2606:2626:0804/084411.009101:ERROR:nss_util.cc(286)] After loading Root Certs, loaded==false: NSS error code: -8018mesa: for the --simplifycfg- sink-common option: may only occur zero or one times!mesa: for the -- global-isel-abort option: may only occur zero or one times!mesa: for the --amdgpu-atomic-optimizations option: may only occur zero or one times!mesa: for the --structurizecfg-skip-uniform-regions option: may only occur zero or one times![2636:2636:0804/084411.912737:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu- process. I got the above after rebooting this morning after another Marco crash (https://termbin.com/xy80). Any insight into whether or not this is software, driver, or hardware issue is appreciated. Thanks,Tim On Fri, 2021-07-30 at 08:08 -0400, Tim Cahill wrote: > Posted the following comment to the Mate-desktop issue: > > Had > another hang with the same configuration as a youtube video played > via a > USB headphone (Jabra40). I was able to recover by killing Firefox, > in > which the video was playing. The video became choppy and garbled and > then stopped. The stderr is below: > > ALSA lib conf.c:5187:(snd_config_expand) Unknown parameters 1ALSA lib > control.c:1379:(snd_ctl_open_noupdate) Invalid CTL sysdefault:1ALSA > lib conf.c:5187:(snd_config_expand) Unknown parameters 2ALSA lib > control.c:1379:(snd_ctl_open_noupdate) Invalid CTL sysdefault:2ALSA > lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slaveALSA lib > pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slaveALSA lib > pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slaveALSA lib > pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slaveALSA lib > pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave > > On re-launch of Firefox from terminal window, the following appeared: > > [GFX1-]: More than 1 GPU from same vendor detected via PCI, cannot > deduce deviceOn Thu, 2021-07-29 at 12:04 -0400, Tim Cahill wrote: > > I apologize if the name callout is disconcerting. I was trying to > > follow instructions for sending bugs and saw your name listed as > > the owner of this code area. > > FYI, I'd done some more troubleshooting and tinkering regarding the > > crashing and Mate seems to be at the center of all the issues. As a > > result, I also opened an Issue with the Mate Desktop team ( > > https://github.com/mate-desktop/mate-panel/issues/1242). Mate also > > has a power management component, which is probably responsible for > > the excess logging and the confusion over Navil10. However, I have > > no way to vouch for now accurately the Mate PM applet gathered data > > for its instantiation. I have no external devices connected that > > I'm aware would use it since I thought that was via HDMI. I *do* > > have a Jabra Evolve2 headset that uses the TypeC USB connector, but > > I assume that's not using the GPU. > > The issue documentation I left with Mate notes that if I launch > > apps from a terminal that is NOT launched from the Mate panel > > (right-click on desktop instead to open terminal), the parent for > > all the apps (Firefox, Evolution, etc.) is separate from Mate (at > > least separate from mate-panel). Everything has worked fine (except > > for the constant logging of the wake-up action) since I've done > > that (and turned off the screensaver and screensaver lock). So, I'm > > not sure what else to do at this point. Please advise if I should > > do anything on the driver side. > > Thanks,Tim > > On Thu, 2021-07-29 at 11:14 -0400, Felix Kuehling wrote: > > > Am 2021-07-28 um 12:10 p.m. schrieb Tim Cahill: > > > > Hi Felix, > > > > > > I'm not sure why you're calling me out by name. I'm not working > > > onanything obviously related to your crashes. > > > Anyway, I took a quick look at the backtraces. They all point at > > > libgdk.Two of them are segfaults, one is an abort. It's not clear > > > how thesewould be related to the GPU driver. That said, when you > > > boot withnomodeset, the GPU driver and all HW acceleration is > > > completelydisabled. If that makes the problem disappear, the GPU > > > driver is clearlyinvolved in the problem in some way. > > > The abort points at a problem while freeing memory. This could be > > > causedby a double-free problem in some unrelated code, possibly > > > related to theGPU driver. This would be a problem in a user mode > > > component (maybeMesa), not the kernel mode driver. > > > I believe the messages you're seeing when you move the mouse are > > > theresult of runtime power management that puts the GPU to sleep > > > when it'sidle and reinitializes it when it's needed. You have 2 > > > GPUs in yourlaptop, an integrated Renoir GPU in the Ryzen CPU, > > > and an externalNavi10 GPU for higher gaming performance. The GPU > > > that goes to sleep andwakes up is the external Navi10 GPU. > > > The OpenGL renderer string
Re: Linux Mint 20.04 5.11 issue
Posted the following comment to the Mate-desktop issue: Had another hang with the same configuration as a youtube video played via a USB headphone (Jabra40). I was able to recover by killing Firefox, in which the video was playing. The video became choppy and garbled and then stopped. The stderr is below: ALSA lib conf.c:5187:(snd_config_expand) Unknown parameters 1 ALSA lib control.c:1379:(snd_ctl_open_noupdate) Invalid CTL sysdefault:1 ALSA lib conf.c:5187:(snd_config_expand) Unknown parameters 2 ALSA lib control.c:1379:(snd_ctl_open_noupdate) Invalid CTL sysdefault:2 ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave On re-launch of Firefox from terminal window, the following appeared: [GFX1-]: More than 1 GPU from same vendor detected via PCI, cannot deduce device On Thu, 2021-07-29 at 12:04 -0400, Tim Cahill wrote: > I apologize if the name callout is disconcerting. I was trying to > follow instructions for sending bugs and saw your name listed as the > owner of this code area. > FYI, I'd done some more troubleshooting and tinkering regarding the > crashing and Mate seems to be at the center of all the issues. As a > result, I also opened an Issue with the Mate Desktop team ( > https://github.com/mate-desktop/mate-panel/issues/1242). Mate also > has a power management component, which is probably responsible for > the excess logging and the confusion over Navil10. However, I have no > way to vouch for now accurately the Mate PM applet gathered data for > its instantiation. I have no external devices connected that I'm > aware would use it since I thought that was via HDMI. I *do* have a > Jabra Evolve2 headset that uses the TypeC USB connector, but I assume > that's not using the GPU. > The issue documentation I left with Mate notes that if I launch apps > from a terminal that is NOT launched from the Mate panel (right-click > on desktop instead to open terminal), the parent for all the apps > (Firefox, Evolution, etc.) is separate from Mate (at least separate > from mate-panel). Everything has worked fine (except for the constant > logging of the wake-up action) since I've done that (and turned off > the screensaver and screensaver lock). So, I'm not sure what else to > do at this point. Please advise if I should do anything on the driver > side. > Thanks,Tim > On Thu, 2021-07-29 at 11:14 -0400, Felix Kuehling wrote: > > Am 2021-07-28 um 12:10 p.m. schrieb Tim Cahill: > > > Hi Felix, > > > > I'm not sure why you're calling me out by name. I'm not working > > onanything obviously related to your crashes. > > Anyway, I took a quick look at the backtraces. They all point at > > libgdk.Two of them are segfaults, one is an abort. It's not clear > > how thesewould be related to the GPU driver. That said, when you > > boot withnomodeset, the GPU driver and all HW acceleration is > > completelydisabled. If that makes the problem disappear, the GPU > > driver is clearlyinvolved in the problem in some way. > > The abort points at a problem while freeing memory. This could be > > causedby a double-free problem in some unrelated code, possibly > > related to theGPU driver. This would be a problem in a user mode > > component (maybeMesa), not the kernel mode driver. > > I believe the messages you're seeing when you move the mouse are > > theresult of runtime power management that puts the GPU to sleep > > when it'sidle and reinitializes it when it's needed. You have 2 > > GPUs in yourlaptop, an integrated Renoir GPU in the Ryzen CPU, and > > an externalNavi10 GPU for higher gaming performance. The GPU that > > goes to sleep andwakes up is the external Navi10 GPU. > > The OpenGL renderer string specifies "RENOIR". Therefore I'm > > surprisedthat the Navi10 GPU wakes up when you move the mouse. > > Ideally itshouldn't be used at all when you're just using the > > desktop. > > If you suspect that runtime power management is responsible for > > yourproblems, you could disable it with amdgpu.runpm=0 on the > > kernel commandline. That means the Navi10 GPU won't go into the low > > power mode anddrain your battery more quickly. So this is not a > > permanent solution.Just an experiment to narrow down the problem. > > Regards, Felix > > > > > I'm not sure how to do this as I haven't had to report a bug > > > before.I've looked to a variety of bug reporting sites to see if > > > anyone elseis running into the same issues that I'm having (such > > > as the Mateproject) and haven't seen anything at all similar to > > > the issue I'mhaving. Since I had issues with AMD drivers with my > > > distro (infobelow) and some consistent and high volume dmesg > > > content shows up,I've decided that I should start here with the > > > AMD kernel
Re: Linux Mint 20.04 5.11 issue
I apologize if the name callout is disconcerting. I was trying to follow instructions for sending bugs and saw your name listed as the owner of this code area. FYI, I'd done some more troubleshooting and tinkering regarding the crashing and Mate seems to be at the center of all the issues. As a result, I also opened an Issue with the Mate Desktop team ( https://github.com/mate-desktop/mate-panel/issues/1242). Mate also has a power management component, which is probably responsible for the excess logging and the confusion over Navil10. However, I have no way to vouch for now accurately the Mate PM applet gathered data for its instantiation. I have no external devices connected that I'm aware would use it since I thought that was via HDMI. I *do* have a Jabra Evolve2 headset that uses the TypeC USB connector, but I assume that's not using the GPU. The issue documentation I left with Mate notes that if I launch apps from a terminal that is NOT launched from the Mate panel (right-click on desktop instead to open terminal), the parent for all the apps (Firefox, Evolution, etc.) is separate from Mate (at least separate from mate-panel). Everything has worked fine (except for the constant logging of the wake-up action) since I've done that (and turned off the screensaver and screensaver lock). So, I'm not sure what else to do at this point. Please advise if I should do anything on the driver side. Thanks,Tim On Thu, 2021-07-29 at 11:14 -0400, Felix Kuehling wrote: > Am 2021-07-28 um 12:10 p.m. schrieb Tim Cahill: > > Hi Felix, > > I'm not sure why you're calling me out by name. I'm not working > onanything obviously related to your crashes. > Anyway, I took a quick look at the backtraces. They all point at > libgdk.Two of them are segfaults, one is an abort. It's not clear how > thesewould be related to the GPU driver. That said, when you boot > withnomodeset, the GPU driver and all HW acceleration is > completelydisabled. If that makes the problem disappear, the GPU > driver is clearlyinvolved in the problem in some way. > The abort points at a problem while freeing memory. This could be > causedby a double-free problem in some unrelated code, possibly > related to theGPU driver. This would be a problem in a user mode > component (maybeMesa), not the kernel mode driver. > I believe the messages you're seeing when you move the mouse are > theresult of runtime power management that puts the GPU to sleep when > it'sidle and reinitializes it when it's needed. You have 2 GPUs in > yourlaptop, an integrated Renoir GPU in the Ryzen CPU, and an > externalNavi10 GPU for higher gaming performance. The GPU that goes > to sleep andwakes up is the external Navi10 GPU. > The OpenGL renderer string specifies "RENOIR". Therefore I'm > surprisedthat the Navi10 GPU wakes up when you move the mouse. > Ideally itshouldn't be used at all when you're just using the > desktop. > If you suspect that runtime power management is responsible for > yourproblems, you could disable it with amdgpu.runpm=0 on the kernel > commandline. That means the Navi10 GPU won't go into the low power > mode anddrain your battery more quickly. So this is not a permanent > solution.Just an experiment to narrow down the problem. > Regards, Felix > > > I'm not sure how to do this as I haven't had to report a bug > > before.I've looked to a variety of bug reporting sites to see if > > anyone elseis running into the same issues that I'm having (such as > > the Mateproject) and haven't seen anything at all similar to the > > issue I'mhaving. Since I had issues with AMD drivers with my distro > > (infobelow) and some consistent and high volume dmesg content shows > > up,I've decided that I should start here with the AMD kernel team. > > I have a fairly new MSI laptop with the following configuration: > > [code]System:Kernel: 5.11.0-25-generic x86_64 bits: 64 > > compiler: N/ADesktop: MATE 1.24.0 wm: marcodm: LightDM > > Distro: Linux Mint 20.2 Uma base: Ubuntu > > 20.04focal Machine: Type: Laptop System: Micro-Star product: > > Alpha 17 A4DEK v:REV:1.0 serial: Chassis: type: > > 10 serial: Mobo: Micro-Star model: MS-17EK v: > > REV:1.0 serial: UEFI: American Megatrendsv: > > E17EKAMS.101 date: 10/26/2020 Battery: ID-1: BAT1 charge: 66.2 Wh > > condition: 67.0/65.7 Wh (102%)volts: 12.4/10.8model: > > MSI Corp. MS-17EK serial: N/A status: Unknown CPU: Topology: > > 8-Core model: AMD Ryzen 7 4800H with RadeonGraphics bits: 64 type: > > MT MCParch: Zen rev: 1 L2 cache: 4096 > > KiBflags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 > > sse4_2 sse4assse3 svm bogomips: 92630Speed: 4278 MHz > > min/max: 1400/2900 MHz Core speeds (MHz):1: 4280 2: 1865 3: > > 13974: 2188 5: 1489 6: 2265 7: 1907 8: 1906 9: 1729 10: > > 139711: 1397 12: 1397 13: 139714: 1397 15: 1907 16: > > 1740 Graphics: Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT >
Re: Linux Mint 20.04 5.11 issue
Am 2021-07-28 um 12:10 p.m. schrieb Tim Cahill: > Hi Felix, I'm not sure why you're calling me out by name. I'm not working on anything obviously related to your crashes. Anyway, I took a quick look at the backtraces. They all point at libgdk. Two of them are segfaults, one is an abort. It's not clear how these would be related to the GPU driver. That said, when you boot with nomodeset, the GPU driver and all HW acceleration is completely disabled. If that makes the problem disappear, the GPU driver is clearly involved in the problem in some way. The abort points at a problem while freeing memory. This could be caused by a double-free problem in some unrelated code, possibly related to the GPU driver. This would be a problem in a user mode component (maybe Mesa), not the kernel mode driver. I believe the messages you're seeing when you move the mouse are the result of runtime power management that puts the GPU to sleep when it's idle and reinitializes it when it's needed. You have 2 GPUs in your laptop, an integrated Renoir GPU in the Ryzen CPU, and an external Navi10 GPU for higher gaming performance. The GPU that goes to sleep and wakes up is the external Navi10 GPU. The OpenGL renderer string specifies "RENOIR". Therefore I'm surprised that the Navi10 GPU wakes up when you move the mouse. Ideally it shouldn't be used at all when you're just using the desktop. If you suspect that runtime power management is responsible for your problems, you could disable it with amdgpu.runpm=0 on the kernel command line. That means the Navi10 GPU won't go into the low power mode and drain your battery more quickly. So this is not a permanent solution. Just an experiment to narrow down the problem. Regards, Felix > > I'm not sure how to do this as I haven't had to report a bug before. > I've looked to a variety of bug reporting sites to see if anyone else > is running into the same issues that I'm having (such as the Mate > project) and haven't seen anything at all similar to the issue I'm > having. Since I had issues with AMD drivers with my distro (info > below) and some consistent and high volume dmesg content shows up, > I've decided that I should start here with the AMD kernel team. > > I have a fairly new MSI laptop with the following configuration: > > [code] > System:Kernel: 5.11.0-25-generic x86_64 bits: 64 compiler: N/A > Desktop: MATE 1.24.0 wm: marco > dm: LightDM Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 > focal > Machine: Type: Laptop System: Micro-Star product: Alpha 17 A4DEK v: > REV:1.0 serial: > Chassis: type: 10 serial: > Mobo: Micro-Star model: MS-17EK v: REV:1.0 serial: > UEFI: American Megatrends > v: E17EKAMS.101 date: 10/26/2020 > Battery: ID-1: BAT1 charge: 66.2 Wh condition: 67.0/65.7 Wh (102%) > volts: 12.4/10.8 > model: MSI Corp. MS-17EK serial: N/A status: Unknown > CPU: Topology: 8-Core model: AMD Ryzen 7 4800H with Radeon > Graphics bits: 64 type: MT MCP > arch: Zen rev: 1 L2 cache: 4096 KiB > flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a > ssse3 svm bogomips: 92630 > Speed: 4278 MHz min/max: 1400/2900 MHz Core speeds (MHz): > 1: 4280 2: 1865 3: 1397 > 4: 2188 5: 1489 6: 2265 7: 1907 8: 1906 9: 1729 10: 1397 > 11: 1397 12: 1397 13: 1397 > 14: 1397 15: 1907 16: 1740 > Graphics: Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / > 5700/5700 XT] > vendor: Micro-Star MSI driver: amdgpu v: kernel bus ID: > 03:00.0 chip ID: 1002:731f > Device-2: AMD Renoir vendor: Micro-Star MSI driver: amdgpu > v: kernel bus ID: 08:00.0 > chip ID: 1002:1636 > Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati > unloaded: fbdev,modesetting,radeon,vesa compositor: marco > resolution: 1920x1080~144Hz > OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.11.0-25-generic > LLVM 11.0.0) > v: 4.6 Mesa 20.2.6 direct render: Yes > Audio: Device-1: AMD Navi 10 HDMI Audio vendor: Micro-Star MSI > driver: snd_hda_intel v: kernel > bus ID: 03:00.1 chip ID: 1002:ab38 > Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio > Processor vendor: Micro-Star MSI > driver: N/A bus ID: 08:00.5 chip ID: 1022:15e2 > Device-3: AMD Family 17h HD Audio vendor: Micro-Star MSI > driver: snd_hda_intel > v: kernel bus ID: 08:00.6 chip ID: 1022:15e3 > Sound Server: ALSA v: k5.11.0-25-generic > Network: Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus > ID: 04:00.0 > chip ID: 8086:2723 > IF: wlp4s0 state: up mac: > Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit > Ethernet vendor: Micro-Star MSI > driver: r8169 v: kernel port: f000 bus ID: 05:00.0 chip ID: > 10ec:8168 > IF: eno1 state: down mac: > Drives:Local Storage: total: 476.94 GiB
