After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 636298 - r600c: gnome-shell crash in overview mode
r600c: gnome-shell crash in overview mode
Status: RESOLVED NOTGNOME
Product: gnome-shell
Classification: Core
Component: drivers
2.91.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
: 636250 640074 642560 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-12-02 14:44 UTC by Stefano Facchini
Modified: 2012-08-23 17:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gdb output at shell crash (2.95 KB, text/plain)
2010-12-02 15:15 UTC, António Lima
  Details
backtrace (199.79 KB, text/plain)
2010-12-03 00:07 UTC, António Lima
  Details
debugging backtrace (15.29 KB, application/octet-stream)
2010-12-03 10:14 UTC, Stefano Facchini
  Details
r600c driver fix (5.18 KB, patch)
2011-02-08 20:28 UTC, Alexander Larsson
rejected Details | Review

Description Stefano Facchini 2010-12-02 14:44:24 UTC
With gnome-shell 2.91.2 and 2.91.3, whenever I try to select a window in overview mode, or try to type something in the search box, the shell crashes printing the following messages

radeonSetSpanFunctions: bad format: 0x0002
radeonSetSpanFunctions: bad format: 0x0002
Shell killed with signal 11

I am using the latest ati driver 6.13.99 and mesa driver r600g compiled from source.
Comment 1 António Lima 2010-12-02 15:15:10 UTC
I'm having the same issue with the same error messages.

I'm running fedora 14 up-to-date with radeon drivers. My video card is an ATI RadeonHD 3400 (rv620).

I tried to get a trace running --replace -g but when the shell crashes I'm unable to return from overview mode and I can't get the trace.

I'll attach what I could get from gdb.
Comment 2 António Lima 2010-12-02 15:15:39 UTC
Created attachment 175713 [details]
gdb output at shell crash
Comment 3 Fabio Durán Verdugo 2010-12-02 17:42:27 UTC
please try this.
- Run 'gnome-shell --replace --sync -g'
- (gdb) r
<reproduce crash>
- (gdb) backtrace
Comment 4 António Lima 2010-12-03 00:07:23 UTC
Created attachment 175746 [details]
backtrace

I was able to get the backtrace by launching gnome-shell in a VT and sending the output to a text file.

I hope there's everything there.

Please let me know if I can provide any thing else.

Thanks!
Comment 5 Owen Taylor 2010-12-03 00:13:59 UTC
It's basically bizarre to me that this would occur both with:
 
 latest mesa r600 Gallium driver
 F14 radeon drivers (r600 classic)

since it clearly looks like a driver bug. I've also tested the shell with success with a very recent version of the R600 gallium drivers.

As a starter, I'd like to see people's results from running:

 $ glxinfo | grep renderer
Comment 6 António Lima 2010-12-03 00:45:24 UTC
Here goes mine

glxinfo | grep renderer
OpenGL renderer string: Mesa DRI R600 (RV620 95C4) 20090101  TCL DRI2
Comment 7 Stefano Facchini 2010-12-03 10:14:21 UTC
Created attachment 175765 [details]
debugging backtrace
Comment 8 Stefano Facchini 2010-12-03 10:17:57 UTC
Here is mine 

glxinfo | grep renderer

OpenGL renderer string: Mesa DRI R600 (CEDAR 68E0) 20090101 x86/MMX/SSE2 TCL DRI2

Maybe this is unrelated, but starting the shell I also obtain the following:

Gtk-Message: Failed to load module "gnomesegvhandler": libgnomesegvhandler.so: cannot open shared object file: No such file or directory
      JS LOG: GNOME Shell started at Fri Dec 03 2010 11:17:02 GMT+0100 (CET)

(mutter:5123): Gvc-WARNING **: Connection failed, reconnecting...

(mutter:5123): GdmUser-WARNING **: Unable to load CK history: no seat-id found

(mutter:5123): Gvc-WARNING **: Connection failed, reconnecting...

[...]
Comment 9 Stefano Facchini 2010-12-03 11:04:46 UTC
Ok, I wasn't using the gallium driver, just the classic r600 :)

I confirm that with the proper Gallium driver gnome-shell does not crash anymore...

glxinfo | grep renderer
OpenGL renderer string: Gallium 0.4 on AMD CEDAR

sorry for the confusion
Comment 10 Florian Müllner 2010-12-03 11:57:01 UTC
(In reply to comment #9)
> sorry for the confusion

Don't be sorry for telling us that open source beats proprietary :-)
Comment 11 Owen Taylor 2010-12-03 15:51:21 UTC
(In reply to comment #9)
> Ok, I wasn't using the gallium driver, just the classic r600 :)
> 
> I confirm that with the proper Gallium driver gnome-shell does not crash
> anymore...
> 
> glxinfo | grep renderer
> OpenGL renderer string: Gallium 0.4 on AMD CEDAR
> 
> sorry for the confusion

Ah, that makes more sense now :-) .. hmm, r600 classic is sort of a dead driver going forward. Not sure how much work it's worth to debug problems there and get fixes done.

(In reply to comment #10)
> (In reply to comment #9)
> > sorry for the confusion
> 
> Don't be sorry for telling us that open source beats proprietary :-)

Actually, it's just two different open source drivers.
Comment 12 Owen Taylor 2010-12-03 20:14:36 UTC
(In reply to comment #1)
> I'm having the same issue with the same error messages.
> 
> I'm running fedora 14 up-to-date with radeon drivers. My video card is an ATI
> RadeonHD 3400 (rv620).

We now have a yum repsitory:

 http://people.freedesktop.org/~ajax/f14-bling-repo/

With f14 rebuilds of the bleeding edge f15 packages for the graphics. Little or no testing yet, but we'll try to keep it up to date.
Comment 13 António Lima 2010-12-09 12:48:47 UTC
(In reply to comment #12)
> (In reply to comment #1)
> > I'm having the same issue with the same error messages.
> > 
> > I'm running fedora 14 up-to-date with radeon drivers. My video card is an ATI
> > RadeonHD 3400 (rv620).
> 
> We now have a yum repsitory:
> 
>  http://people.freedesktop.org/~ajax/f14-bling-repo/
> 
> With f14 rebuilds of the bleeding edge f15 packages for the graphics. Little or
> no testing yet, but we'll try to keep it up to date.

Thanks, I'll try the repo then. Although I can't it very much since gnome-shell really does not run without KMS enabled and I've been struggling with a KMS bug (GPU lockup) for several Fedora releases now. But I'll give it a try.
Comment 14 Owen Taylor 2010-12-09 23:25:22 UTC
*** Bug 636250 has been marked as a duplicate of this bug. ***
Comment 15 Luca Ferretti 2010-12-10 02:14:34 UTC
(In reply to comment #11)
> 
> Ah, that makes more sense now :-) .. hmm, r600 classic is sort of a dead driver
> going forward. Not sure how much work it's worth to debug problems there and
> get fixes done.

Same here. No more crashes using gallium. However some recent changes in mutter|clutter|gnome-shell trigged this issues: I had no issue with r600 classic one month ago.

Now the question is: will gallium become non-experimental (and widely adopted by distro) before GNOME 3.0.0? :) It's not so trivial enable it.
Comment 16 Johannes Schmid 2010-12-10 13:07:02 UTC
Same problem here, seems r600 (here it is rv635 aka Radeon HD3650) is affected. gnome-shell worked on the same device with jhbuild from end of November so something seems to have introduced this afterwards.
Comment 17 Owen Taylor 2010-12-10 15:25:36 UTC
(In reply to comment #15)
> (In reply to comment #11)
> > 
> > Ah, that makes more sense now :-) .. hmm, r600 classic is sort of a dead driver
> > going forward. Not sure how much work it's worth to debug problems there and
> > get fixes done.
> 
> Same here. No more crashes using gallium. However some recent changes in
> mutter|clutter|gnome-shell trigged this issues: I had no issue with r600
> classic one month ago.

Recent changes probably did trigger this (http://bugzilla.clutter-project.org/show_bug.cgi?id=2414 is one candidate) but it's clearly a Mesa bug, and also things worked fine for me with the 7.10 version of the r600c driver in testing I did a few weeks ago. Coding around driver bugs that have been fixed already isn't something we want to do .
 
> Now the question is: will gallium become non-experimental (and widely adopted
> by distro) before GNOME 3.0.0? :) It's not so trivial enable it.

I can't answer for any other distribution, but R600g will be the driver shipped Fedora 15 along with GNOME 3.0 (and since the Fedora maintainers are a large chunk of the upstream maintainers, that's a pretty clear sign of upstream opinion.
Comment 18 Luca Ferretti 2011-02-08 14:48:25 UTC
Owen, so could we close this as NOTGNOME? The only "solution" could be introduce a workaround in clutter, but I suspect ebassi will never approve it :)
Comment 19 Alexander Larsson 2011-02-08 20:28:53 UTC
Created attachment 180415 [details] [review]
r600c driver fix

I believe this patch fixes the problem
Comment 20 Owen Taylor 2011-02-10 18:58:49 UTC
Review of attachment 180415 [details] [review]:

Marking "rejected" so this doesn't appear on the gnome-shell patches to review list. As long as people are hitting this bug, find it useful to keep it open even if it's NOTGNOME.
Comment 21 Owen Taylor 2011-02-17 13:45:00 UTC
*** Bug 642560 has been marked as a duplicate of this bug. ***
Comment 22 Fabio Durán Verdugo 2011-04-26 12:21:39 UTC
*** Bug 640074 has been marked as a duplicate of this bug. ***
Comment 24 Florian Müllner 2012-08-23 17:37:54 UTC
(In reply to comment #20)
> As long as people are hitting this bug, find it useful to keep it open
> even if it's NOTGNOME.

No more reports for over a year, so I guess we can close this now ...