Bug 636295

Summary:

[RV380] kernel: radeon 0000:01:00.0: ee469400 reserve failed for wait

Product:

[Fedora] Fedora

Reporter:

Eddie Lania <eddie>

Component:

xorg-x11-drv-ati

Assignee:

Jérôme Glisse <jglisse>

Status:

CLOSED NEXTRELEASE

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

medium

Docs Contact:

Priority:

medium

Version:

CC:

forthommel, maciek.borzecki, mcepl, nicofo, stuart, xgl-maint

Target Milestone:

---

Keywords:

Triaged

Target Release:

---

Hardware:

All

OS:

Linux

Whiteboard:

[cat:lockup]

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2011-07-14 16:11:48 UTC

Type:

---

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
dmesg	none
/var/log/messages	none
/var/log/Xorg.0.log	none
dmesg	none
Xorg.0.log	none
messages	none

Description Eddie Lania 2010-09-21 20:45:57 UTC

Description of problem: Just surfing the internet using firefox my computer hangs randomly. This has been introduced since the last kernel upgrade.

My log is filling up with this message:

kernel: radeon 0000:01:00.0: ee469400 reserve failed for wait

This happens when playing flash games like:

http://www.spele.nl/game/meppen/sloop_het_kasteel.html

Current kernel version: 2.6.34.7-56.fc13.i686.PAE

I did not have this using kernel kernel-PAE-2.6.33.3-85.fc13.i686


Version-Release number of selected component (if applicable):

xorg-x11-drv-ati-6.13.0-1.fc13.i686

How reproducible: Always when playing flash game


Steps to Reproduce:
1. Surf around the web until machine locks up.
2. Play flash games and watch syslog.
3.
  
Actual results: Machine locks up, hard reset needed.


Expected results: No lock ups, no errors.


Additional info:

Comment 1 nicofo 2011-01-12 23:44:40 UTC

Related problem here:

1) dmesg also regularly shows lines like:
[  301.817747] radeon 0000:01:00.0: dc336a00 reserve failed for wait
[  325.516984] radeon 0000:01:00.0: dc336a00 reserve failed for wait
[  326.277989] radeon 0000:01:00.0: dc336a00 reserve failed for wait
[ 5730.117530] radeon 0000:01:00.0: ef9e7000 reserve failed for wait
[ 5736.148148] radeon 0000:01:00.0: ef9e7000 reserve failed for wait
[ 5769.003544] radeon 0000:01:00.0: ef9e7000 reserve failed for wait

I don't know what causes them.

2) I tried the link http://www.spele.nl/...  =>  it adds the lines beginning with "[57..]" in dmesg above => I can also reproduce it. Except that Fedora doesn't locks up (lukilly because I have these errors in dmesg every day !)

3) However I can add that I have still sometimes a lock up after xscreensaver (hard reset needed) (not every time, but my screensaver is a random screensaver)
It's probably related.

VERSIONS
Fedora 14
kernel 2.6.35.10-74.fc14.i686
xorg-x11-drv-ati-6.13.1-0.3.20100705git37b348059.fc14.i686

Comment 2 Matěj Cepl 2011-01-24 09:32:12 UTC

Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 3 nicofo 2011-01-24 19:25:19 UTC

Created attachment 475027 [details]
dmesg

Here are the requested files after rebooting with drm.debug=0x04 kernel option:
Remark: after restarting I went to "spele.nl/..." website so that the lines "reserve failed for wait" appears in dmesg

* no xorg.conf
* dmesg attached
* /var/log/messages attached
* /var/log/Xorg.0.log attached

Thanks for reviewing this issue.

Comment 4 nicofo 2011-01-24 19:25:59 UTC

Created attachment 475028 [details]
/var/log/messages

Comment 5 nicofo 2011-01-24 19:26:32 UTC

Created attachment 475029 [details]
/var/log/Xorg.0.log

Comment 6 Matěj Cepl 2011-01-25 11:17:14 UTC

Reporter, could we get information from you, please?

Comment 7 Eddie Lania 2011-01-25 20:22:36 UTC

Created attachment 475263 [details]
dmesg

/var/log/dmesg

Comment 8 Eddie Lania 2011-01-25 20:23:52 UTC

Created attachment 475264 [details]
Xorg.0.log

/var/log/Xorg.0.log

Comment 9 Eddie Lania 2011-01-25 20:24:33 UTC

Created attachment 475265 [details]
messages

/var/log/messages

Comment 10 Matěj Cepl 2011-01-26 16:57:51 UTC

This bug seems to have duplicates in bug 651362, bug 652374, and bug 655101.

Comment 11 nicofo 2011-01-28 19:00:26 UTC

(In reply to comment #10)
> This bug seems to have duplicates in bug 651362, bug 652374, and bug 655101.

I can confirm bug 652374 : as I told in comment 1 , I have sometimes problem with xscreensaver. I have had it with GLmatrix: it causes a log out of the kde desktop. But this doesn't happen every time (it's even unusual: say every 10 times)

Comment 12 Nathanael Noblet 2011-03-09 18:17:13 UTC

I have just recently started to get this in my logs - or at least started to notice them in my logs. Nothing freezing, no other noticable issues (though the internet has seemed extremely slow via firefox) but I can't see how this is related.

2.6.35.11-83.fc14.x86_64

Mar  9 11:04:38 iridium kernel: [343532.909126] radeon 0000:03:00.0: ffff8801cf592200 reserve failed for wait
Mar  9 11:04:40 iridium kernel: [343534.774468] radeon 0000:03:00.0: ffff8801cf592200 reserve failed for wait
Mar  9 11:04:40 iridium kernel: [343535.022548] radeon 0000:03:00.0: ffff8801cf592200 reserve failed for wait
Mar  9 11:04:41 iridium kernel: [343535.680061] radeon 0000:03:00.0: ffff8801cf592200 reserve failed for wait
Mar  9 11:04:42 iridium kernel: [343537.139005] radeon 0000:03:00.0: ffff8801cf592200 reserve failed for wait
Mar  9 11:04:44 iridium kernel: [343538.881999] radeon 0000:03:00.0: ffff8801cf592200 reserve failed for wait
Mar  9 11:05:36 iridium kernel: [343590.841961] radeon 0000:03:00.0: ffff8801d6ac3c00 reserve failed for wait
Mar  9 11:06:14 iridium kernel: [343628.994206] radeon 0000:03:00.0: ffff880017911c00 reserve failed for wait
Mar  9 11:06:17 iridium kernel: [343631.818012] radeon 0000:03:00.0: ffff880017911c00 reserve failed for wait
Mar  9 11:06:19 iridium kernel: [343633.647716] radeon 0000:03:00.0: ffff880017911c00 reserve failed for wait

Comment 13 Maciek Borzecki 2011-04-26 17:30:18 UTC

Started hitting this recently on a Thinkpad T60, Mobility Radeon X1300 64M GPU, after I enabled compiz. I guess, there might be direct relation to fancy 3D graphics then. The extract from messages:
Apr 25 22:06:00 corsair kernel: [ 3244.600928] radeon 0000:01:00.0: f02e7000 reserve failed for wait
Apr 25 22:06:01 corsair kernel: [ 3244.817308] radeon 0000:01:00.0: f02e7000 reserve failed for wait
Apr 25 22:06:03 corsair kernel: [ 3247.250575] radeon 0000:01:00.0: f02e7000 reserve failed for wait
Apr 25 22:06:04 corsair kernel: [ 3247.730783] radeon 0000:01:00.0: f02e7000 reserve failed for wait
Apr 25 22:06:04 corsair kernel: [ 3247.850749] radeon 0000:01:00.0: f02e7000 reserve failed for wait
Apr 25 22:06:04 corsair kernel: [ 3247.916985] radeon 0000:01:00.0: f02e7000 reserve failed for wait
Apr 25 22:06:04 corsair kernel: [ 3248.271784] radeon 0000:01:00.0: f02e7000 reserve failed for wait
Apr 25 22:06:05 corsair kernel: [ 3248.871250] radeon 0000:01:00.0: f02e7000 reserve failed for wait
Apr 25 22:06:05 corsair kernel: [ 3248.999229] radeon 0000:01:00.0: f02e7000 reserve failed for wait
Apr 25 22:06:05 corsair kernel: [ 3249.634139] radeon 0000:01:00.0: f02e7000 reserve failed for wait

Relevant packages below:
xorg-x11-server-Xorg-1.9.5-1.fc14.i686
mesa-libGL-7.9-5.fc14.i686
mesa-libGLU-7.9-5.fc14.i686
kernel-2.6.35.11-83.fc14.i686
kernel-2.6.35.12-88.fc14.i686
xorg-x11-drv-ati-6.13.1-0.4.20100705git37b348059.fc14.i686
mesa-dri-drivers-7.9-5.fc14.i686

The simplest way to trigger this (at least for me) is:
* desktop + compiz (compiz set with minimum effects - shadows, window scaling etc.)
* start openttd, play for a couple of minutes

I'll try with nomodeset and see if I get the same results.

Let me know if there's anything else needed.

Comment 14 Maciek Borzecki 2011-05-11 16:39:06 UTC

It seems that I can't really check with nomodeset as Xorg keeps on crashing with this: https://bugzilla.redhat.com/show_bug.cgi?id=659979
Waiting for F15 to come out and verify if the problem is still present there.

Comment 15 Matěj Cepl 2011-07-12 09:21:16 UTC

(In reply to comment #14)
> Waiting for F15 to come out and verify if the problem is still present there.

OK, giving you NEEDINFO to see what happens next.

Comment 16 Eddie Lania 2011-07-12 15:13:51 UTC

Without compiz (now that gome-shell has become the new window manager) i am unable to reproduce this on fc15.

Comment 17 Matěj Cepl 2011-07-12 15:43:12 UTC

(In reply to comment #16)
> Without compiz (now that gome-shell has become the new window manager) i am
> unable to reproduce this on fc15.

There is compiz available in repos, but honestly ... if gnome-shell works correctly (which is a bit less demanding than compiz), I would be happy.

Does actually gnome-shell work for you?

Comment 18 Eddie Lania 2011-07-12 17:44:21 UTC

It works. But i miss the blurred window borders (windows 7 style). To bad it cannot work together with compiz.

Comment 19 Maciek Borzecki 2011-07-13 21:12:24 UTC

Haven't seen that particular problem on F15, so it's either fixed or just didn't happen yet.

Comment 20 Eddie Lania 2011-07-14 15:08:54 UTC

Yes, I also tested classic gnome with compiz enabled and it seems to be solved now.

Comment 21 Jérôme Glisse 2011-07-14 16:11:48 UTC

Closing reopen if you hit it against f15

Comment 22 nicofo 2011-07-17 13:09:22 UTC

Same for me: tested in F15: no more lines "reserve failed for wait" in dmesg.