[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#860534: marked as done (firmware-amd-graphics: Random system freezes with AMD GPU)

Your message dated Fri, 30 Apr 2021 19:14:22 +0200
with message-id <YIw67llVTYaWQhxL@eldamar.lan>
and subject line Re: Bug#860534: drm/radeon: Change the default to PCI on PowerPC
has caused the Debian Bug report #860534,
regarding firmware-amd-graphics: Random system freezes with AMD GPU
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
860534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860534
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: firmware-amd-graphics
Version: 20161130-2
Severity: important

Dear Maintainer,

Since my update to stretch, my system is randomly freezing after some time of use. The freezes do not require any intensive graphics use, it happened opening a new tab on firefox, and another time firing up Vim on terminal.

This is the pertinent kern.log

Apr 16 00:24:15 venus kernel: [ 3823.269564] radeon 0000:01:00.0: ring 0 stalled for more than 10172msec
Apr 16 00:24:15 venus kernel: [ 3823.269572] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000002b53c last fence id 0x000000000002b554 on ring 0)
Apr 16 00:24:16 venus kernel: [ 3823.781490] radeon 0000:01:00.0: ring 0 stalled for more than 10684msec
Apr 16 00:24:16 venus kernel: [ 3823.781498] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000002b53c last fence id 0x000000000002b554 on ring 0)
Apr 16 00:24:16 venus kernel: [ 3824.293468] radeon 0000:01:00.0: ring 0 stalled for more than 11196msec
Apr 16 00:24:16 venus kernel: [ 3824.293476] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000002b53c last fence id 0x000000000002b554 on ring 0)
Apr 16 00:24:17 venus kernel: [ 3824.805484] radeon 0000:01:00.0: ring 0 stalled for more than 11708msec
Apr 16 00:24:17 venus kernel: [ 3824.805492] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000002b53c last fence id 0x000000000002b555 on ring 0)
Apr 16 00:24:18 venus kernel: [ 3825.317515] radeon 0000:01:00.0: ring 0 stalled for more than 12220msec
Apr 16 00:24:18 venus kernel: [ 3825.317523] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000002b53c last fence id 0x000000000002b555 on ring 0)
Apr 16 00:24:18 venus kernel: [ 3825.829429] radeon 0000:01:00.0: ring 0 stalled for more than 12732msec
Apr 16 00:24:18 venus kernel: [ 3825.829437] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000002b53c last fence id 0x000000000002b555 on ring 0)
Apr 16 00:24:19 venus kernel: [ 3826.341456] radeon 0000:01:00.0: ring 0 stalled for more than 13244msec
Apr 16 00:24:19 venus kernel: [ 3826.341460] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000002b53c last fence id 0x000000000002b559 on ring 0)
Apr 16 00:24:19 venus kernel: [ 3826.553557] radeon 0000:01:00.0: Saved 1367 dwords of commands on ring 0.

The lspci from this GPU: 

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] (prog-if 00 [VGA controller])
        Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 5770]
        Flags: bus master, fast devsel, latency 0, IRQ 33
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Memory at fbdc0000 (64-bit, non-prefetchable) [size=128K]
        I/O ports at ce00 [size=256]
        [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Legacy Endpoint, MSI 00
        Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
        Capabilities: [150] Advanced Error Reporting
        Kernel driver in use: radeon
        Kernel modules: radeon

After the freeze occours I need to reboot the machine, I cannot restart the X server nor open another virtual console, and in one case I got some files corrupted when the system crashed firing up vim.  


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

firmware-amd-graphics depends on no packages.

firmware-amd-graphics recommends no packages.

Versions of packages firmware-amd-graphics suggests:
ii  initramfs-tools  0.127

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi Mathieu,

On Mon, Sep 10, 2018 at 02:12:14PM +0200, Mathieu Malaterre wrote:
> rafael,
> 
> On Sat, Sep 8, 2018 at 4:02 PM Salvatore Bonaccorso <carnil@debian.org> wrote:
> >
> > Control: tags -1 + moreinfo
> >
> > Hi Mathieu,
> >
> > On Tue, Aug 28, 2018 at 02:18:33PM +0200, Mathieu Malaterre wrote:
> > > Control: tags -1 fixed-upstream patch upstream
> > >
> > > The symptoms should disappear now that default has been set to PCI
> > > (instead of AGP) on PowerPC system.
> > >
> > > https://github.com/torvalds/linux/commit/037d1a66ae64
> > >
> > > Target is 4.18-rc1
> > >
> > > https://lkml.org/lkml/2018/6/5/1158
> >
> > Can you confirm if the issue is fixed? If so, can you close this
> > bugreport, the first one including the commits should be
> > 4.18~rc3-1~exp1 .
> 
> Would you please answer Salvatore's question ?
> 
> I was not paying attention enough and the original report seems to
> have been done against x86 arch, while in my specific case (and
> although symptoms are 100% identical) the fix only target ppc32 arch.

Given lack of response I'm now inclided to close the bug for now.

In case the issue still persist, rafael, then please reopen in case it
is reproducbile with a recent kernel from unstable or
buster-backports.

Regards,
Salvatore

--- End Message ---
Reply to: