Bug 97827 - (EE) [mi] EQ overflowing -> freeze
Summary: (EE) [mi] EQ overflowing -> freeze
Status: RESOLVED NOTOURBUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.5 (2009.10)
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-15 20:11 UTC by Jérôme
Modified: 2017-01-11 10:10 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg.log (16.85 KB, text/plain)
2016-09-15 20:11 UTC, Jérôme
no flags Details
glxinfo (59.54 KB, text/plain)
2016-09-16 20:22 UTC, Jérôme
no flags Details

Description Jérôme 2016-09-15 20:11:19 UTC
Created attachment 126563 [details]
xorg.log

My system froze. I waited a few minutes but nothing happened. I could not "Ctrl+1", I had to REISUB.

I'm running a Debian Jessie with a Radeon R7 240 GPU

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]

using the free radeon driver (xserver-xorg-video-ati (1:7.5.0-1)) and a recent kernel:

4.6.0-0.bpo.1-amd64 #1 SMP Debian 4.6.4-1~bpo8+1 (2016-08-11) x86_64 GNU/Linux

Attaching log excerpt.

Since it only happened once, I'm not sure there's much we can do with this.

I'm not even sure this is the right place to report this.

If there's anything useful I can get via ssh from another machine when it happens, please tell me.

(I also asked on StackExchange: http://unix.stackexchange.com/questions/308959/ee-mi-eq-overflowing-freeze)
Comment 1 Michel Dänzer 2016-09-16 08:31:23 UTC
It looks like the GPU hangs. Please attach the corresponding dmesg output as well, captured after the problem occurred, and the output of glxinfo.
Comment 2 Jérôme 2016-09-16 08:38:58 UTC
OK, if this ever occurs again, I'll try to SSH from another machine and get both dmesg and glxinfo outputs.
Comment 3 Michel Dänzer 2016-09-16 08:46:18 UTC
You can get the glxinfo output anytime FWIW.
Comment 4 Jérôme 2016-09-16 20:22:49 UTC
Created attachment 126583 [details]
glxinfo
Comment 5 Michel Dänzer 2016-09-21 02:11:18 UTC
If it happens again, any chance you can try a newer version of Mesa?
Comment 6 Jérôme 2016-09-21 07:32:43 UTC
I suppose I should get a new version of Mesa before it happens again.

I'm currently using Debian Jessie. If there is a more recent version available in the repos (backport, or even compatible package in testing), I don't mind.

I can also move to testing if required.

Please point me to the right package or set of packages.

Thanks.
Comment 7 Paul Wise 2016-09-21 08:49:01 UTC
There is a newer version of mesa in Debian jessie-backports:

http://backports.debian.org/Instructions/
https://packages.debian.org/source/stable-backports/mesa

This command should upgrade all the mesa packages you have installed:

aptitude -t jessie-backports upgrade '?source-package("^mesa$")~i'
Comment 8 Jérôme 2016-09-22 13:44:35 UTC
Done. Thanks for the command line.

aptitude -t jessie-backports upgrade '?source-package("^mesa$")~i'
Resolving dependencies...                
The following NEW packages will be installed:
  libdrm-amdgpu1{a} 
The following packages will be REMOVED:
  libegl1-mesa-drivers{u} libopenvg1-mesa{u} 
The following packages will be upgraded:
  libdrm2 libegl1-mesa libgbm1 libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libgles1-mesa libgles2-mesa libwayland-egl1-mesa libxatracker2 
10 packages upgraded, 1 newly installed, 2 to remove and 152 not upgraded.
Comment 9 Jérôme 2017-01-10 22:51:47 UTC
In case that matters, I just discovered the driver needs a proprietary firmware which was not installed.
Comment 10 Michel Dänzer 2017-01-11 09:52:12 UTC
(In reply to Jérôme from comment #9)
> In case that matters, I just discovered the driver needs a proprietary
> firmware which was not installed.

There's no evidence of missing microcode in the files attached to this report.

Did the freeze occur again?
Comment 11 Jérôme 2017-01-11 10:10:01 UTC
> There's no evidence of missing microcode in the files attached to this report.

I discovered that while investigating https://bugs.freedesktop.org/show_bug.cgi?id=99337

From what I understand, due to this, I was not even using radeon but a generic fallback driver... So it wouldn't be a radeon issue.

> Did the freeze occur again?

A few freezes occurred (2, maybe 3) but I can't tell if those were due the same cause. I didn't have the time or available secondary machine to get necessary info (ssh log from another machine, demsg, glxinfo) when it happened.

I'm closing this for now as "NOTOURBUG". I'll reopen if it occurs again and I can get necessary info (Xorg log, dmesg, glxinfo).


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.