[RS690M] No 3d acceleration in Radeon X1200 with new Gallium r300 / 3d drivers in 11.04 (Needs kernel quirk)

[André Oliva]

The bug is active also in Freedesktop.org : https://bugs.freedesktop.org/show_bug.cgi?id=37679

[edit]
The bug seems to be fixed with a patch provided by Freedesktop.org team.
[/edit]

[edit]
This bug is caused by interrupts. They're not working. The solution for this problem is:
- To see if Ubuntu 10.04 (where all things worked well) used UMS instead of KMS.
- If Lucid used KMS, to bisect the kernel to see what change caused the problem.

[/edit]

[edit]
The bug description, updated:

The symptoms: No 3d acceleration (glxgears shows a black window, Unity doesn't start), *but* no fallback into the software-rendering mode (glxinfo reports that the 3d acceleration is working)

The hardware: ATI Radeon RS690M X1200 series

The version of Ubuntu: Ubuntu 11.04 (final release) [and Maverick also]. The behavior was also observed in Debian and Fedora 15, as noted below (so it seems not to be Ubuntu-specific).

The version of xserver-xorg-video-ati: 1:6.14.0-0ubuntu4 (default in Natty). Same problems with the xorg-edgers PPA in Natty Beta2.

The software affected: Compiz (doesn't start because requires direct rendering); then, Unity (just the wallpaper or black screen and the mouse pointer). glxgears, Stellarium, Blender, Adobe Flash Player in fullscreen mode and Visual module of Python work if software rendering is forced (but of course they run very very slow).

The history of the bug: all worked as expected (out of the box) in 10.04, but in 10.10 the problems started. The workaround was to disable KMS, but now, in Maverick, since the new Gallium driver doesn't have a non-KMS mode, that workaround is not available. This issue was reported when using 11.04 Beta 1 and Beta 2, then, in the descriptions below there are some strange things (xorg crash during startup, software rendering fallback), that don't occur any more. The issue is just the description given here.

The exceptions: **sometimes** (??) the 3d acceleration does work as expected, but at the moment there is no way for us to know when it will work or not [help please!]. And, sometimes the 3d acceleration work but is so slow that it seems to be actually software rendering.

The workarounds: `vblank_mode=0 glxgears` (or other program) gives correct 3d accelerated output. `export vblank_mode=0` also allows to start Compiz and 3d acceleration works after running that. That is just a workaround and the problem is not solved yet.

[/edit]
Binary package hint: xorg

I installed Ubuntu 11.04 Beta 1, and I'm not able to run Unity and Compiz, because I have no 3d acceleration. However, I was able to run Compiz once, the next time I booted, I don't know why, Compiz doesn't work. After several reboots, I see the following:

1. Sometimes (?), I have 3d acceleration via software rendering. When I run `glxinfo | grep render` I get:
direct rendering: Yes
OpenGL renderer string: Software Rasterizer
    GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_fragment_program,
And if I run `compiz --replace`, I get the following error:

Backend : gconf
Integration : true
Profile : default
Adding plugins
Initializing core options...done
Initializing bailer options...done
Initializing detection options...done
Initializing composite options...done
Compiz (opengl) - Fatal: GLX_EXT_texture_from_pixmap is missing
Compiz (opengl) - Fatal: Software rendering detected
Compiz (bailer) - Info: Ensuring a shell for your session
prueba@prueba:~$ Window manager warning: Locale not understood by C library, internationalization will not work

(metacity:2357): Gtk-WARNING **: Locale not supported by C library.
 Using the fallback 'C' locale.
Window manager warning: last_user_time (1302379766) is greater than comparison timestamp (1200358). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Window manager warning: 0x3401006 (prueba@pru) appears to be one of the offending windows with a timestamp of 1302379766. Working around...
Window manager warning: 0x340103e (prueba@pru) appears to be one of the offending windows with a timestamp of 1302379766. Working around...

prueba@prueba:~$ Window manager warning: last_user_time (1302379766) is greater than comparison timestamp (1228188). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Window manager warning: 0x340103e (prueba@pru) appears to be one of the offending windows with a timestamp of 1302379766. Working around...
Window manager warning: Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x340103e (prueba@pru)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.

From Xorg.0.log:
[ 261.329] (II) AIGLX: Screen 0 is not DRI2 capable
[ 261.329] drmOpenDevice: node name is /dev/dri/card0
[ 261.329] drmOpenDevice: open result is 12, (OK)
[ 261.330] drmOpenByBusid: Searching for BusID pci:0000:01:05.0
[ 261.330] drmOpenDevice: node name is /dev/dri/card0
[ 261.330] drmOpenDevice: open result is 12, (OK)
[ 261.330] drmOpenByBusid: drmOpenMinor returns 12
[ 261.330] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[ 261.330] drmOpenByBusid: drmGetBusid reports pci:0000:01:05.0
[ 261.330] (II) AIGLX: Trying DRI driver /usr/lib/dri/r300_dri.so
[ 261.394] (EE) AIGLX error: Calling driver entry point failed
[ 261.420] (EE) AIGLX: reverting to software rendering

2. Sometimes, I have direct 3d acceleration, but it's unusable. glxgears doesn't work (black window). Also, if I run compiz, I get a blank screen (no Unity, no windows, just the mouse pointer and the background image). In this case, if I run `glxinfo | grep render`, I get:

direct rendering: Yes
OpenGL renderer string: Gallium 0.4 on ATI RS690
    GL_NV_blend_square, GL_NV_conditional_render, GL_NV_light_max_exponent,

So, I'm using the Gallium driver. I had a similar problem with Maverick and the radeon driver. I solved the problem turning off the Kernel Mode Setting (# echo options radeon modeset=0 > /etc/modprobe.d/radeon-kms.conf). I don't know how to do that with the Gallium driver. I want also to try using the radeon driver, but I don't know how to do it.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: xorg 1:7.6+4ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: wl
Architecture: i386
CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
CompositorRunning: None
Date: Sat Apr 9 14:02:35 2011
DistUpgraded: Fresh install
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 5.100.82.38+bdcom, 2.6.38-7-generic, i686: installed
 bcmwl, 5.100.82.38+bdcom, 2.6.38-8-generic, i686: installed
GraphicsCard:
 ATI Technologies Inc RS690M [Radeon X1200 Series] [1002:791f] (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:01fd]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
MachineType: Dell Inc. Inspiron 1721
ProcEnviron:
 LANGUAGE=es_CR:en
 LANG=es_CR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=f00be871-e8f8-4c57-83dc-3d166efb4e78 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/03/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0UK441
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd02/03/2008:svnDellInc.:pnInspiron1721:pvr:rvnDellInc.:rn0UK441:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1721
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.4+bzr20110407-0ubuntu2
version.libdrm2: libdrm2 2.4.23-1ubuntu5
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.1-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu6

[André Oliva (gandreoliva)]

I see that this bug is closely related to Bug #715330 , but even if the symptoms are the same, I'm running the version of the Kernel that they say has the fix released, and also, I tried the workaround described on comment #17 and that doesn't solve my problem.

[André Oliva (gandreoliva)]

This is my Xorg.0.log when I have software rendering. I see that there is an error in the line 746, that forces to revert to software rendering (line 747), but the lines 663, 671 and 674 show that the direct rendering was enabled. What does it mean?

[Phil (phil-redhat-bugs)]

Created attachment 493306
dmesg

Description of problem:
Gnome3 doesn't start properly from the Gnome3 live CD.

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

How reproducible:

Steps to Reproduce:
1. Get HP Compaq 6715b laptop.
2. Boot from F15 beta live CD

Actual results:
Cursor appears, gnome vertical striped blue background appears. Mouse cursor moves. Panel doesn't appear, just get blue background and nothing else. Mouse clicks are ignored. Desktop completely unusable.

Expected results:
Panel should appear at top. Mouse clicks should do something.

Additional info:
telinit 3, then startx *sometimes* gets the panel and activities panels to display, but then the desktop hangs with only the cursor being moveable.

[Phil (phil-redhat-bugs)]

Created attachment 493307
lspci -vv

[Phil (phil-redhat-bugs)]

Created attachment 493308
.xsession-errors

[Phil (phil-redhat-bugs)]

Created attachment 493309
Xorg.0.log

[Bryce Harrington (bryce)]

Two answer one of your questions, the gallium driver does not have a non-KMS mode, so the modeset=0 workaround isn't available there. (With some work you may be able to revert to using the non-gallium radeon driver, but let's focus this bug report on fixing the bug itself.)

[Bryce Harrington (bryce)]

What is the output of this command?

$ ls /etc/alternatives/gl_conf -l

Also, did you do a full reinstall or an upgrade?

You don't need /etc/X11/xorg.conf, may as well remove it - the driver will automatically load radeon.

[Ben (threadstone)]

same problem here with x1200 and Natty reinstall (but also with Fedora 15)...

$ ls /etc/alternatives/gl_conf -l
lrwxrwxrwx 1 root root 24 Apr 8 13:20 /etc/alternatives/gl_conf -> /usr/lib/mesa/ld.so.conf

[André Oliva (gandreoliva)]

Output of `ls /etc/alternatives/gl_conf -l`:
lrwxrwxrwx 1 root root 24 Apr 8 12:42 /etc/alternatives/gl_conf -> /usr/lib/mesa/ld.so.conf

the same of Ben.

@Bryce Harrington: Ah, I understand now (about KMS)... I installed Beta 1 from scratch, and I will try now to install Beta 2 also from scratch to see if something has changed. At the moment I have removed the xorg.conf file.

[André Oliva (gandreoliva)]

Ah, I forgot to mention that I installed also the most recent drivers from the xorg-edgers PPA, but that didn't helped. And also I'm having problems when I boot (GDM doesn't start). I'm attaching the Xorg.1.log file, and I see that there is an error parsing the config file (?). I'll install Beta 2 to see if something has changed, including this strange error.

[Bryce Harrington (bryce)]

[ 17.844] Parse error on line 15 of section Screen in file /etc/X11/xorg.conf
 "EndSectionSection" is not a valid keyword in this section.

Typo in your xorg.conf

[Bryce Harrington (bryce)]

@Ben, can you file a new bug report via 'ubuntu-bug xorg' and then set it as a dupe to this bug? (Or just paste the bug # here). André's bug is quite odd, so I'd like to compare and contrast your logs with his. Also, there's several ways one could end up with no 3D so I'd like to rule those out in your case.

[André Oliva (gandreoliva)]

@Bryce Harrington: The problem parsing the file is another very strange problem, it occurs "sometimes", and other times I can boot normally as right now. By this reason I will try to install Beta 2 (to see if it's something already fixed). I also thought that it was a typo in my xorg.conf but right now I don't have a xorg.conf file in my /etc/X11 directory.

[Bryce Harrington (bryce)]

Check if you have anything in /etc/X11/xorg.conf.d/

Also check the timestamp on your Xorg.1.log to make sure it's not just a left over from some earlier boot.

[André Oliva (gandreoliva)]

Ok, I have installed in another partition Ubuntu 11.04 Beta 2 and this is what I found:
1. No 3d acceleration
2. No booting problems (3 boots without any kind of problem)
3. When I try to start unity/compiz --replace I get a blank screen (just the wallpaper and mouse).
4. Everything in the Xorg.0.log file looks fine, but I still have no 3d acceleration.
5. When I run `glxgears`, I get a blank window (see attachment)
6. When I run `glxinfo | grep render` I get this:
direct rendering: Yes
OpenGL renderer string: Gallium 0.4 on ATI RS690
    GL_NV_blend_square, GL_NV_conditional_render, GL_NV_light_max_exponent,

And...
7. I booted up editing the GRUB command line: I added "nomodeset", and I got software rendering.
So, the problem is not related to the two errors that appear on Xorg.0.log... (I'm sorry, when I reported the bug [Beta 1] I forgot that I forced the system to use "nomodeset"...)

[Ben (threadstone)]

filed Bug #768236

[Phil (phil-redhat-bugs)]

This may be a dupe of bug 683687.

[André Oliva (gandreoliva)]

After booting several times and trying to use Ubuntu, I got again 3d acceleration, but after rebooting, no 3d acceleration again (Compiz doesn't start, glxgears as in the screenshot). This is the same behavior that I observed in Maverick, but I solved that disabling KMS. Now, with the Gallium 3d drivers, as noted by Bryce, that workaround is not an option. All I can do for now is to install Unity-2d and to use software rasterization (`export LIBGL_ALWAYS_SOFTWARE=1` and then executing the program), and activating Metacity composition, but of course, software rasterization is very slow and it's "acceptable" only if the window of the program is very small... It's strange. In Lucid radeon driver worked fine and out of the box...

[Martín Ferrari (tincho)]

I have a similar issue.

I installed Natty a couple of days ago. When Unity came up, it was sluggish and many apps crashed. I switched to "classic with no effects", and continued setting up stuff. Later I realised that hardware acceleration was not working. I fixed it (don't remember how), and the problems became worse.

Since my idea for this machine is to use it as a media center, I installed many of this apps, and thought that there were buggy, as I could only see blank screens.

Later I realised that not even glxgears works. If I disable KMS, or set LIBGL_ALWAYS_SOFTWARE=1, they work, but so slow that the apps are unusable.

I have already tried installing the propietary drivers, which tell me that my card is unsupported. I installed the X edgers drivers, with no improvement. Tried different xorg.conf tweaks that I found on the 'net, no dice.

As most of these media apps for some reason require 3d accel (stupid shiny effects), I need to make this work.

$ lspci |grep VGA
01:05.0 VGA compatible controller: ATI Technologies Inc RS690M [Radeon X1200 Series]

$ glxinfo |grep render
direct rendering: Yes
OpenGL renderer string: Gallium 0.4 on ATI RS690
    GL_NV_blend_square, GL_NV_conditional_render, GL_NV_light_max_exponent,

[André Oliva (gandreoliva)]

@Martín: Yes, it's the same problem I have... Radeon X1200 is no longer supported by ADM (???!!!), and, of course, software rasteriaztion is really slow.

I installed Natty (final release), and have the same problem.

It's a good idea to report a bug in freedesktop.org?

[Martín Ferrari (tincho)]

Hi André,

On Sun, May 1, 2011 at 15:09, André Oliva <email address hidden> wrote:
> @Martín: Yes, it's the same problem I have... Radeon X1200 is no longer
> supported by ADM (???!!!), and, of course, software rasteriaztion is
> really slow.
>
> I installed Natty (final release), and have the same problem.
>
> It's a good idea to report a bug in freedesktop.org?

Dunno... In debian the hardware accel works (according to glxinfo),
but is as slow as soft render...
--
Martín Ferrari

[André Oliva (gandreoliva)]

But as I noted in comment #17, "sometimes" I do have 3d acceleration
working, and I've seen that sometimes the 3d acc. is very slow, just as you
said; and sometimes, I'm lucky and 3d acc. works as expected. But about 70%
of times 3d acc. fails, and at the moment I'm unable to predict when 3d will
work or not. By this reason I think it's not Ubuntu-specific.

El 01/05/2011 12:46, "Martín Ferrari" <email address hidden> escribió:

Hi André,

On Sun, May 1, 2011 at 15:09, André Oliva <email address hidden> wrote:
> @Martín: Yes, it's t...
Dunno... In debian the hardware accel works (according to glxinfo),
but is as slow as soft render...
--
Martín Ferrari

--
You received this bug notification because you are a direct subscriber
of the bug.
https://bugs...

[Brian Ealdwine (eode)]

This is a duplicate of bug #556782.

This bug has a bug open on xorg, which appears not to be moving.

[Martín Ferrari (tincho)]

Brian, thanks for the heads up!

[André Oliva (gandreoliva)]

Yes, thank you...

[Brian Ealdwine (eode)]

:-) You're absolutely welcome.

[Brian Ealdwine (eode)]

I was incorrect when I marked this as a duplicate of the other bug (or at least it's not definitely the same issue).
I hate when that happens to a bug I'm working on, and apologize for any inconvenience.

Martin, I've re-subscribed you as I believe your reasoning for unsubscribing was that this bug was marked duplicate, and I think you need to be informed.

[Phil (phil-redhat-bugs)]

Still get problem with latest nightly of Fedora 15, Fedora-15-Nightly-20110518.06-i686-Live-desktop.iso. Only way to get boot (from live CD and after installing to harddisk) is by adding "nomodeset" to the kernel paremeters on boot.

[Matěj (matj-redhat-bugs)]

In my opinion, this is not an Xorg issue, but something about gdm or gnome-session. Reassigning.

[André Oliva (gandreoliva)]

This is a bug reported in Launchpad, against the "xserver-xorg-video-ati" package of Ubuntu, on 2011-04-10. There, the bug is marked as Confirmed.

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/755791

The symptoms: No 3d acceleration (glxgears shows a black window, Unity [Ubuntu 11.04 3d shell] doesn't start), *but* no fallback into the software-rendering mode (glxinfo reports that the 3d acceleration is working)

The hardware: ATI Radeon RS690M X1200 series

The Operating system: Ubuntu 11.04 (final release) [and Maverick also]. The behavior was also observed in Debian and Fedora 15, as noted in the original bug report (so it seems not to be Ubuntu-specific).

The version of xserver-xorg-video-ati: 1:6.14.0-0ubuntu4 (default in Natty). Same problems with the xorg-edgers PPA in Natty Beta2. (If you want that I test the lastest packages from git, please give me instructions).

The software affected: Compiz (doesn't start because requires direct rendering); then, Unity (just the wallpaper or black screen and the mouse pointer).. Glxgears, Stellarium, Blender, Adobe Flash Player in fullscreen mode and Visual module of Python work if software rendering is forced (but of course they run very very slow).

The history of the bug: all worked as expected (out of the box) in Ubuntu 10.04 LTS, but in 10.10 the problems started. The workaround was to disable KMS, but now, in Natty, since the new Gallium driver doesn't have a non-KMS mode, that workaround is not available.

The situations when it works: **sometimes** (??!! please help to determine when!!) the 3d acceleration does work as expected, but at the moment there is no way for us to know when it will work or not [help please!]. And, sometimes the 3d acceleration works but is so slow that it seems to be actually software rendering.

The workarounds: none known. Just enabling temporarily software rendering (as described below), but that really isn't a workaround. In Ubuntu 10.10 the workaround was to turn of KMS. As noted, that doesn't work any more.

There are Xorg.0.log (comment #15 of the original bug report) and screenshots (comment #13 in the original bug report)

Also, the bug was incorrectly marked as a duplicate of the bug #556782 in Launchpad, reported here as the bug 35457 .

Thank you in advance.

[Phil (phil-redhat-bugs)]

I'm pretty sure this is an Xorg issue with the driver and this specific graphics chip. Problem also reported here:

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/755791

[Phil Cole (filcole)]

Similar problem occurs with fedora 15 with RS690. See https://bugzilla.redhat.com/show_bug.cgi?id=698011

[André Oliva (gandreoliva)]

I filed Bug 37679 in freedesktop.org against xorg. If you have comments, ideas or attachmets please comment the bug report there... Clearly this is a non Ubuntu-specific issue...

https://bugs.freedesktop.org/show_bug.cgi?id=37679

[agd5f (agd5f)]

Looks like the radeon kernel module is not loaded before starting X. The kernel modules must be loaded before starting X.

[André Oliva (gandreoliva)]

Created attachment 47257
Xorg.0.log

This is a fresh Xorg.0.log if you want to check...

[agd5f (agd5f)]

In this case KMS is properly initialized. Is 3D not working?

[André Oliva (gandreoliva)]

That's right, the 3D acceleration is not working in that case (glxgears results in a black window). But when it does work, the Xorg.0.log looks the same (I'm not sure if something changes).

[agd5f (agd5f)]

Does glxgears work if you disable vsync?

vblank_mode=0 glxgears

Can you also attach the output of glxinfo?

[Phil Cole (filcole)]

I'm the person experiencing problems on Fedora 15 - I think it's related to this problem. Only if I include NoModeSet in the kernel parameters will GNOME3 start. 90% of the time only the background appears (no panel, no activities) and then it hangs. Very occassionally will Gnome4 start, but it soon hangs.

KDE4 will start OK without NoModeSet, this is where the following attachments are from.
  Xorg.0.log-KDE4
  lspci-vv.txt
  lsmod.txt
  glxgears.txt
  glxinfo.txt

Note that under KDE4:
  "glxgears" just gives a black window, without any gears!
  "vblank_mode=0 glxgears" gives the correct output with approx 62-80fps.

==============
p.s. I started to have problems with X hanging completely (in KDE4 or GNOME2) on Fedora 14. X completely locks up, The display no longer updates, but does not become corrupted, but all inputs are blocked. Only the cursor moves. The laptop fan comes on 100% and I can only do reboot via the power button to get things moving again. I am still experiencing these problems with Fedora 15 - setting NoModeSet does not stop this problem occuring.

[Phil Cole (filcole)]

Created attachment 47355
glxgears run under KDE (NoModeSet is NOT in kernel params)

[Phil Cole (filcole)]

Created attachment 47356
glxinfo run under KDE (NoModeSet is NOT in kernel params)

[Phil Cole (filcole)]

Created attachment 47357
lspci -vv

[Phil Cole (filcole)]

Created attachment 47358
Xorg.0.log run under KDE (NoModeSet is NOT in kernel params)

[agd5f (agd5f)]

(In reply to comment #6)
> "glxgears" just gives a black window, without any gears!
> "vblank_mode=0 glxgears" gives the correct output with approx 62-80fps.

It looks like interrupts aren't working on your system. If you run:
cat /proc/interrupts
while running X do you see the numbers increasing for the interrupt used by radeon?

[Phil Cole (filcole)]

Running cat /proc/interrupts under X does NOT have any increasing numbers for radeon.

Further info: This problem is intermittent. On my last reboot I started KDE4, and was able to run "vblank_mode=0 glxgears", "glxgears" and then boot into Gnome3 all successfully. Throughout this /proc/interrupts remained the same for the radeon line.

See attached*-gnome3-hang.txt files.

[Phil Cole (filcole)]

Created attachment 47380
/proc/interrupts when gnome3 hangs and after killing X and starting KDE4

[Phil Cole (filcole)]

Created attachment 47382
Xorg.0.log when gnome3 hangs (NoModeSet is NOT on kernel params)

[Phil (phil-redhat-bugs)]

Upstream freedesktop.org bug:
https://bugs.freedesktop.org/show_bug.cgi?id=37679
In upstream bug have found that interrupts are not being generated for radeon in /proc/interrupts.

Moved from gdm back to Xorg ati component.

[agd5f (agd5f)]

Does booting with pci=nomsi on the kernel command line in grub help?

[Phil Cole (filcole)]

(In reply to comment #15)
> Does booting with pci=nomsi on the kernel command line in grub help?

No this doesn't make any difference - I still get:
1. /proc/interrupts doesn't change for the radeon line.
2. "glxgears" gives a black window. "vblank_mode=0 glxgears" works OK.
3. GNOME3 hanging on startup.

See attached Xorg.0.log-pci=nomsi.txt

[Phil Cole (filcole)]

Created attachment 47402
Xorg.0.log with pci=nomsi no kernel params

[André Oliva (gandreoliva)]

"vblank_mode=0 glxgears" works also for me! I can use normal 3d acceleration with that method. Stellarium and Glxgears work well: fast, smooth, as expected. But "vblank_mode=0 compiz --replace" does not work (I get a blank screen with the mouse pointer).

[agd5f (agd5f)]

(In reply to comment #18)
> "vblank_mode=0 glxgears" works also for me! I can use normal 3d acceleration
> with that method. Stellarium and Glxgears work well: fast, smooth, as expected.
> But "vblank_mode=0 compiz --replace" does not work (I get a blank screen with
> the mouse pointer).

compiz is a script, so you'll probably have to set vblank_mode as a global env var
export vblank_mode=0
compiz --replace

Still, it's just a workaround. For some reason, interrupts are not working on your system.

[André Oliva (gandreoliva)]

As noted in the freedesktop.org bug reported, running "vblank_mode=0 glxgears" or "vblank_mode=0 [name_of_application]" works, but Compiz still doesn't start. Workaround found. Does this workaround work for you?

[André Oliva (gandreoliva)]

Ok, with the "export", compiz also starts. I have to say that Compiz is *very* slow... Almost as software rendering. I don't know why... As a workaround, the 3d acceleration works better if the program is started from Metacity (??).

[André Oliva (gandreoliva)]

Compiz works after running "export vblank_mode=0", and then "compiz --replace" or logging out and then logging into Unity 3d, for me that works, but very slow. As noted in freedesktop.org, this is just a *workaround* and something is bad at the moment. This issue is not resolved.

[agd5f (agd5f)]

(In reply to comment #20)
> Ok, with the "export", compiz also starts. I have to say that Compiz is *very*
> slow... Almost as software rendering. I don't know why... As a workaround, the
> 3d acceleration works better if the program is started from Metacity (??).

If you aren't getting interrupts, fences won't work properly, so GL will be slow as well since every fence has to time out before it's retired.

[André Oliva (gandreoliva)]

(In reply to comment #21)
> (In reply to comment #20)
> > Ok, with the "export", compiz also starts. I have to say that Compiz is *very*
> > slow... Almost as software rendering. I don't know why... As a workaround, the
> > 3d acceleration works better if the program is started from Metacity (??).
>
> If you aren't getting interrupts, fences won't work properly, so GL will be
> slow as well since every fence has to time out before it's retired.

I see... Thank you for your explanation...

[André Oliva (gandreoliva)]

I use also the Visual module of python (vpython.org). It's a module for making 3d simulations, and it uses 3d acceleration. I'm getting an extrange error:

ATTENTION: default value of option vblank_mode overridden by environment.
ATTENTION: default value of option vblank_mode overridden by environment.
r300 FP: Compiler Error:
Ran out of hardware temporaries
Using a dummy shader instead.

when I use "export vblank_mode=0; ipython" and run
  > from visual import *
  > sphere()

(I'm getting a black window, where the simulation is supposed to be)

Everything works well in Ubuntu 10.04. Also, I can run simulations (very slowly) with software rendering (and since the simulations are for scientific purposes, the speed of the simulation is highly important). In another computer with a newer ATI graphics card, the problem is not present.

I would like to know if I get this error because of this bug or this is another issue related with vpython...

[agd5f (agd5f)]

(In reply to comment #23)
> I use also the Visual module of python (vpython.org). It's a module for making
> 3d simulations, and it uses 3d acceleration. I'm getting an extrange error:
>
> ATTENTION: default value of option vblank_mode overridden by environment.
> ATTENTION: default value of option vblank_mode overridden by environment.
> r300 FP: Compiler Error:
> Ran out of hardware temporaries
> Using a dummy shader instead.

That is a different bug. Please file a different bug report for that.

[Tommy_CZ (t-kijas)]

I have ATI x1250 and compiz works for me but no game like trackmania can be started and altought compiz works, it is terrible slow. Every move of an window is a pain.

[André Oliva (gandreoliva)]

(In reply to comment #24)
> (In reply to comment #23)
> > I use also the Visual module of python (vpython.org). It's a module for making
> > 3d simulations, and it uses 3d acceleration. I'm getting an extrange error:
> >
> > ATTENTION: default value of option vblank_mode overridden by environment.
> > ATTENTION: default value of option vblank_mode overridden by environment.
> > r300 FP: Compiler Error:
> > Ran out of hardware temporaries
> > Using a dummy shader instead.
>
> That is a different bug. Please file a different bug report for that.

A bug report here or in vpython.org?

[agd5f (agd5f)]

(In reply to comment #25)
> A bug report here or in vpython.org?

Here against the r300 gallium driver.

[Phil Cole (filcole)]

Alex,
I have built the latest radeon driver from git master, and still get the problem of no interrupts in /proc/interrupts. (I do get interrupts on another PC using Radeon HD 4350, RV710.) Can you point me in the direction of where the interrupts might be turned on/off? Is it by the radeon driver, or elsewhere in the kernel? Thanks.

[agd5f (agd5f)]

(In reply to comment #27)
> Alex,
> I have built the latest radeon driver from git master, and still get the
> problem of no interrupts in /proc/interrupts. (I do get interrupts on another
> PC using Radeon HD 4350, RV710.) Can you point me in the direction of where the
> interrupts might be turned on/off? Is it by the radeon driver, or elsewhere in
> the kernel? Thanks.

It could be a hardware or bios problem. The drm just registers an interrupt handler with the core interrupt code in the kernel and enables device specific interrupt sources. You don't seem to be getting any interrupts for the radeon chip so it seems like something is set wrong in the northbridge configuration which is usually handled by the bios. Does your system have a bios upgrade available?

[Phil Cole (filcole)]

(In reply to comment #28)
> .... Does your system have a bios upgrade available?

I've just applied the latest BIOS for the HP Compaq 6715b laptop. I upgraded from F.07 (16/07/2007) to F.0E (25/11/2008) from here: http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3356624&prodTypeId=321957&prodSeriesId=3368540&swLang=13&taskId=135&swEnvOID=1093

After doing this and a vanilla kernel boot (nomodeset not set), and the latest git radeon driver I get: (NOTE: this is a two core system)

0. GNOME3 hangs immediately on startup (so tried KDE4).
1. Whilst booting KDE4 can monitor /proc/interrupts in non-X console and see radeon interupts rising for both CPUs.
2. Can use X under KDE4 and notice radeon interrupts rising (when windows moved etc)
3. Then starting "glxgears" or "vblank_output=0 glxgears" under KDE4 gives a blank window and causes interrupts to no longer be registered in /proc/interrupts! At this point moving windows around becomes noticeably slower. (Sometimes this occurs without needing to run glxgears)
4. Killing X (Ctrl-Alt-Backspace) back to GDM and restarting KDE4 causes interrupts to start being counted again for radeon in /proc/interrupts. BUT interrupts only increase on CPU0. CPU1 does not increase past that counted in step 3.
5. Starting "glxgears" causes all radeon interrupts to stop being counted in /proc/interrupts.
6. Go to step 4 and repeat!

I also got the following messages in syslog. Note radeon is on irq 19.

Jun 4 00:33:54 f15 kernel: [ 900.986231] irq 19: nobody cared (try booting with the "irqpoll" option)
Jun 4 00:33:54 f15 kernel: [ 900.986241] Pid: 3410, comm: knotify4 Not tainted 2.6.38.6-27.fc15.i686 #1
Jun 4 00:33:54 f15 kernel: [ 900.986245] Call Trace:
Jun 4 00:33:54 f15 kernel: [ 900.986256] [<c07ceb2d>] ? printk+0x2d/0x2f
Jun 4 00:33:54 f15 kernel: [ 900.986262] [<c07d00ff>] __report_bad_irq+0x3e/0x86
Jun 4 00:33:54 f15 kernel: [ 900.986269] [<c048820f>] note_interrupt+0xfa/0x153
Jun 4 00:33:54 f15 kernel: [ 900.986274] [<c0488b17>] handle_fasteoi_irq+0x88/0xa6
Jun 4 00:33:54 f15 kernel: [ 900.986279] [<c0488a8f>] ? handle_fasteoi_irq+0x0/0xa6
Jun 4 00:33:54 f15 kernel: [ 900.986282] <IRQ> [<c0404bbd>] ? do_IRQ+0x3c/0x92
Jun 4 00:33:54 f15 kernel: [ 900.986292] [<c0403770>] ? common_interrupt+0x30/0x38
Jun 4 00:33:54 f15 kernel: [ 900.986298] [<c04620fd>] ? arch_local_irq_restore+0x5/0xb
Jun 4 00:33:54 f15 kernel: [ 900.986305] [<c07d62b3>] ? _raw_spin_unlock_irqrestore+0x13/0x15
Jun 4 00:33:54 f15 kernel: [ 900.986310] [<c0732fb2>] ? skb_dequeue+0x48/0x4f
Jun 4 00:33:54 f15 kernel: [ 900.986316] [<c07aa2cf>] ? unix_stream_recvmsg+0x116/0x408
Jun 4 00:33:54 f15 kernel: [ 900.986323] [<c0592f7b>] ? selinux_socket_recvmsg+0x1f/0x22
Jun 4 00:33:54 f15 kernel: [ 900.986329] [<c072e303>] ? sock_aio_read+0xf6/0xfe
Jun 4 00:33:54 f15 kernel: [ 900.986335] [<c043feb7>] ? irq_exit+0x4c/0x70
Jun 4 00:33:54 f15 kernel: [ 900.986342] [<c04e4352>] ? do_sync_read+0x96/0xcf
Jun 4 00:33:54 f15 kernel: [ 900.986348] [<c04e4672>] ? rw_verify_area+0xd0/0xf3
Jun 4 00:33:54 f15 kernel: [ 900.986352] [<c042e4e2>] ? __might_sleep+...

[Matěj (matj-redhat-bugs)]

I agree and believe that it is more appropriate to let it be resolved upstream.

We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.

Thank you for helping to make free software better.

[agd5f (agd5f)]

(In reply to comment #29)
>
> So I tried rebooting with "irqpoll" in the kernel options. KDE4 and GNOME3
> (gnome-shell) both run. glxgears gives 50 FPS !!
>
> So, my guess is the kernel/drm/radeon is wedging on interrupt processing.

Sounds like your board bios has screwed up the irq routing which is not something we can fix in the driver unfortunately.

        irqpoll [HW]
                        When an interrupt is not handled search all handlers
                        for it. Also check all handlers each timer
                        interrupt. Intended to get systems with badly broken
                        firmware running.

[krmolot (krmolot)]

Hardware 3D will work in proprietary legacy 3D driver in Debian Lenny.

[André Oliva (gandreoliva)]

(In reply to comment #30)
> (In reply to comment #29)
> >
> > So I tried rebooting with "irqpoll" in the kernel options. KDE4 and GNOME3
> > (gnome-shell) both run. glxgears gives 50 FPS !!
> >
> > So, my guess is the kernel/drm/radeon is wedging on interrupt processing.
>
> Sounds like your board bios has screwed up the irq routing which is not
> something we can fix in the driver unfortunately.
>
> irqpoll [HW]
> When an interrupt is not handled search all handlers
> for it. Also check all handlers each timer
> interrupt. Intended to get systems with badly broken
> firmware running.

But I have never made an upgrade of BIOS, and 3d acceleration worked in Ubuntu 10.04, but now it doesn't work. In fact, right now I can boot into 10.04 and 3d acceleration works. Isn't the driver responsible for that behavior?

[agd5f (agd5f)]

(In reply to comment #32)
>
> But I have never made an upgrade of BIOS, and 3d acceleration worked in Ubuntu
> 10.04, but now it doesn't work. In fact, right now I can boot into 10.04 and 3d
> acceleration works. Isn't the driver responsible for that behavior?

Did 10.04 use KMS? The UMS code did not rely on irqs as much.

[Phil Cole (filcole)]

(In reply to comment #30)
> (In reply to comment #29)
>
> > So, my guess is the kernel/drm/radeon is wedging on interrupt processing.
>
> Sounds like your board bios has screwed up the irq routing which is not
> something we can fix in the driver unfortunately.

See comment #29, upon initial boot the radeon interrupts are firing when first booted, they then stop for 1 CPU when glxgears runs, and then stop totally after X is killed restarted and glxgears re-runs. What is glxgears doing that affects the routing IRQs in the BIOS???

[André Oliva (gandreoliva)]

(In reply to comment #33)
>
> Did 10.04 use KMS? The UMS code did not rely on irqs as much.

Yes, 10.04 uses KMS by default.

[agd5f (agd5f)]

(In reply to comment #35)
> (In reply to comment #33)
> >
> > Did 10.04 use KMS? The UMS code did not rely on irqs as much.
>
> Yes, 10.04 uses KMS by default.

Bisect the kernel and see what commit broke it.

[agd5f (agd5f)]

Does:
Option "EnablePageFlip" "False"
in the device section of your xorg.conf help?

[Phil Cole (filcole)]

(In reply to comment #37)
> Does:
> Option "EnablePageFlip" "False"
> in the device section of your xorg.conf help?

This thread seems to indicate the cause of stopping interrupts is the dodgy BIOS and ACPI stuff: http://www.gossamer-threads.com/lists/linux/kernel/981060

I'm currently investigating with Fedora 9 & Fedora 10 since *may* be where the problem was introduced.

[krmolot (krmolot)]

Adding "noapic" to grub (GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub in ubuntu) fix this problem for me. also it fix some skype sound problems.

cat /proc/interrupts
           CPU0
  0: 154291 XT-PIC-XT-PIC timer
  1: 2902 XT-PIC-XT-PIC i8042
  2: 0 XT-PIC-XT-PIC cascade
  7: 569 XT-PIC-XT-PIC
  8: 0 XT-PIC-XT-PIC rtc0
  9: 2353 XT-PIC-XT-PIC acpi
 10: 350 XT-PIC-XT-PIC ohci_hcd:usb2, hda_intel
 11: 97805 XT-PIC-XT-PIC ehci_hcd:usb1, ohci_hcd:usb3, ohci_hcd:usb4, ohci_hcd:usb5, ohci_hcd:usb6, ahci, eth1, radeon
 12: 269533 XT-PIC-XT-PIC i8042
 14: 0 XT-PIC-XT-PIC pata_atiixp
 15: 0 XT-PIC-XT-PIC pata_atiixp
 42: 42003 PCI-MSI-edge sky2@pci:0000:02:00.0
NMI: 0 Non-maskable interrupts
LOC: 198285 Local timer interrupts
SPU: 0 Spurious interrupts
PMI: 0 Performance monitoring interrupts
IWI: 0 IRQ work interrupts
RES: 0 Rescheduling interrupts
CAL: 0 Function call interrupts
TLB: 0 TLB shootdowns
TRM: 0 Thermal event interrupts
THR: 0 Threshold APIC interrupts
MCE: 0 Machine check exceptions
MCP: 4 Machine check polls
ERR: 569
MIS: 0
sry for poor eng :)

[krmolot (krmolot)]

I'm add "noapic" to GRUB_CMDLINE_LINUX_DEFAULT line in /etc/default/grub and it's work wor me at last. Also it fix some skype sound problems. But i have x1250 video. If someone have x1200 plz test this workaround solution.

p.s. "vblank_mode=0 glxgears":
3345 frames in 5.0 seconds = 668.866 FPS

cat /proc/interrupts :
11: 143899 XT-PIC-XT-PIC ehci_hcd:usb1, ohci_hcd:usb3, ohci_hcd:usb4, ohci_hcd:usb5, ohci_hcd:usb6, ahci, eth1, radeon

sorry for poor eng :)

[André Oliva (gandreoliva)]

With that line in the Grub, I'm able to start Unity, but it's terribly slow.

glxgears:
55 frames in 5.0 seconds = 10.959 FPS

vblank_mode=0 glxgears:
1302 frames in 5.0 seconds = 260.377 FPS

/proc/interrupts
           CPU0 CPU1
  0: 229673 42359 XT-PIC-XT-PIC timer
  1: 1857 275 XT-PIC-XT-PIC i8042
  2: 0 0 XT-PIC-XT-PIC cascade
  3: 14 6 XT-PIC-XT-PIC firewire_ohci
  5: 24087 9605 XT-PIC-XT-PIC ohci_hcd:usb3, ohci_hcd:usb5, eth0, radeon
  7: 83593 365590 XT-PIC-XT-PIC ehci_hcd:usb1, mmc0, r852
  8: 0 0 XT-PIC-XT-PIC rtc0
  9: 2 0 XT-PIC-XT-PIC acpi, ohci_hcd:usb4, ohci_hcd:usb6
 10: 18453 4682 XT-PIC-XT-PIC ahci
 11: 200 76 XT-PIC-XT-PIC ohci_hcd:usb2, hda_intel
 12: 88865 24737 XT-PIC-XT-PIC i8042
 14: 2610 1842 XT-PIC-XT-PIC pata_atiixp
 15: 0 0 XT-PIC-XT-PIC pata_atiixp
NMI: 0 0 Non-maskable interrupts
LOC: 56514 169570 Local timer interrupts
SPU: 0 0 Spurious interrupts
PMI: 0 0 Performance monitoring interrupts
IWI: 0 0 IRQ work interrupts
RES: 122753 131496 Rescheduling interrupts
CAL: 372 533 Function call interrupts
TLB: 2175 2723 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
MCE: 0 0 Machine check exceptions
MCP: 4 4 Machine check polls
ERR: 245628
MIS: 0

[dima-tr (dima-tr)]

This helped:
- get mesa3d from ftp://ftp.freedesktop.org/pub/mesa/7.10.2/ . Build it following the instructions on http://mesa3d.org which is basically ./configure && make
- sudo cp <mesa>/lib/r300_dri.so /usr/lib/dri/
(and probably the same for radeon_dri.so )

Usual performance for my glxgears 250 fps is back, I had the same and the CPU is down to 0 (yoohoo!), but at some moment during my experiments I had 286 fps (the CPU was still at ~0!). At the moment I have no idea how to reproduce this. The experiments have involved:
1) building x86-ati-driver from the latest sources,
2) building mesa with drmProto,
3) fiddling around with Section "Device" at specially created /usr/share/X11/xorg.conf.d/20-device.conf,
4) copying <mesa>/lib/* to /sr/local/lib/GL and setting in ~/.bashrc
  export LIBGL_DRIVERS_PATH=/usr/local/lib/GL
  export LD_LIBRARY_PATH=/usr/local/lib/GL:$LD_LIBRARY_PATH

Then some parts were left from the rep versions, and some were overwritten. What namely gave a 20% faster combination is a mystery.

I'm synced to the latest Ubuntu 11.04 repositories, xorg-edgers is NOT installed.

[Muhammet Aklan (aklan)]

Hello.

This bug also affects other graphics cards. I have ATI Radeon RV370 X550 and it has the same problem. None of the suggestions above have solved the problem. It started to occur when I installed 11.04, I'm using 11.10 Alpha 3 now and there is still the same problem here.

[krmolot (krmolot)]

(In reply to comment #40)
> With that line in the Grub, I'm able to start Unity, but it's terribly slow.
>
> glxgears:
> 55 frames in 5.0 seconds = 10.959 FPS
>
> vblank_mode=0 glxgears:
> 1302 frames in 5.0 seconds = 260.377 FPS
Noapic is not working for me in amd64 (it switch to software rendering whith 100% CPU usage. In glxinfo it show harware rendering). It work in i386.

[Michel Dänzer (michel-daenzer)]

(In reply to comment #41)
> Noapic is not working for me in amd64 (it switch to software rendering whith
> 100% CPU usage. In glxinfo it show harware rendering).

Try running the app which ends up using software rendering with LIBGL_DEBUG=verbose to see where it's picking up the drivers from.

[krmolot (krmolot)]

(In reply to comment #42)
> Try running the app which ends up using software rendering with
> LIBGL_DEBUG=verbose to see where it's picking up the drivers from.

LIBGL_DEBUG=verbose vblank_mode=0 glxgears
libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so
libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so
ATTENTION: default value of option vblank_mode overridden by environment.
ATTENTION: default value of option vblank_mode overridden by environment.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/ubuntu/.drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/ubuntu/.drirc: No such file or directory.
1081 frames in 5.0 seconds = 216.093 FPS
1133 frames in 5.0 seconds = 226.586 FPS
1129 frames in 5.0 seconds = 225.717 FPS
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 4127 requests (4127 known processed) with 0 events remaining.

LIBGL_DEBUG=verbose glxinfo| fgrep render
libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so
libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/ubuntu/.drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/ubuntu/.drirc: No such file or directory.
direct rendering: Yes
OpenGL renderer string: Gallium 0.4 on ATI RS690
    GL_NV_blend_square, GL_NV_conditional_render, GL_NV_light_max_exponent,
libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so
libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/ubuntu/.drirc: No such file or directory.

[krmolot (krmolot)]

In Ubuntu 11.04 i386:
LIBGL_DEBUG=verbose vblank_mode=0 glxgears
libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so
libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so
ATTENTION: default value of option vblank_mode overridden by environment.
ATTENTION: default value of option vblank_mode overridden by environment.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/krmolot/.drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/krmolot/.drirc: No such file or directory.
3101 frames in 5.0 seconds = 620.159 FPS
3170 frames in 5.0 seconds = 633.798 FPS
3164 frames in 5.0 seconds = 632.756 FPS
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 9864 requests (9864 known processed) with 0 events remaining.

[Michel Dänzer (michel-daenzer)]

(In reply to comment #43)
> libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so

This isn't software rendering. The speed difference may be due to a different 3D driver (r300g vs classic) / version / build (e.g. r300g with/out LLVM support, check with 'strings /usr/lib/dri/r300_dri.so|grep LLVM_') / ...

[krmolot (krmolot)]

(In reply to comment #45)
>
> This isn't software rendering. The speed difference may be due to a different
> 3D driver (r300g vs classic) / version / build (e.g. r300g with/out LLVM
> support, check with 'strings /usr/lib/dri/r300_dri.so|grep LLVM_') / ...
I'm using the same version of distributive:
ubuntu-11.04-desktop-amd64.iso
ubuntu-11.04-desktop-i386.iso
"strings /usr/lib/dri/r300_dri.so|grep LLVM_" nothing is return.

[Michel Dänzer (michel-daenzer)]

(In reply to comment #46)
> "strings /usr/lib/dri/r300_dri.so|grep LLVM_" nothing is return.

In neither case? How about

ldd /usr/lib/dri/r300_dri.so|grep LLVM

[krmolot (krmolot)]

(In reply to comment #47)
> (In reply to comment #46)
> > "strings /usr/lib/dri/r300_dri.so|grep LLVM_" nothing is return.
>
> In neither case?
Yes
> How about
>
> ldd /usr/lib/dri/r300_dri.so|grep LLVM
Nothing

ldd /usr/lib/dri/r300_dri.so
 linux-vdso.so.1 => (0x00007fff225ff000)
 libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f06eaee1000)
 libdricore.so => /usr/lib/dri/libdricore.so (0x00007f06eaaac000)
 libglsl.so => /usr/lib/dri/libglsl.so (0x00007f06ea7a7000)
 libdrm.so.2 => /lib/x86_64-linux-gnu/libdrm.so.2 (0x00007f06ea59c000)
 libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007f06ea372000)
 libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f06ea153000)
 libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f06e9f4f000)
 libdrm_radeon.so.1 => /lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x00007f06e9d48000)
 libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f06e9ac2000)
 libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f06e98ac000)
 libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f06e9518000)
 /lib64/ld-linux-x86-64.so.2 (0x00007f06eb7bc000)
 librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f06e930f000)

ldd /usr/lib/dri/r300_dri.so
 linux-gate.so.1 => (0x00387000)
 libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0x00110000)
 libdricore.so => /usr/lib/dri/libdricore.so (0x00388000)
 libglsl.so => /usr/lib/dri/libglsl.so (0x001fb000)
 libdrm.so.2 => /lib/i386-linux-gnu/libdrm.so.2 (0x002eb000)
 libexpat.so.1 => /lib/i386-linux-gnu/libexpat.so.1 (0x002f5000)
 libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0x0076d000)
 libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0x0031f000)
 libdrm_radeon.so.1 => /lib/i386-linux-gnu/libdrm_radeon.so.1 (0x00704000)
 libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0x00323000)
 libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0x00349000)
 libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0x0097c000)
 /lib/ld-linux.so.2 (0x00616000)
 librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0x00365000)

Notebook: emachines d620, video: x1250

[Michel Dänzer (michel-daenzer)]

Actually, I think the lack of LLVM support explains the difference: IIRC, without LLVM the Gallium software vertex processing code uses assembly optimizations on 32 bit but not on 64 bit. Current upstream r600g refuses to build without LLVM, so this should clear up on its own at some point. Maybe you can try current oneiric live CDs.

[krmolot (krmolot)]

(In reply to comment #49)
> Actually, I think the lack of LLVM support explains the difference: IIRC,
> without LLVM the Gallium software vertex processing code uses assembly
> optimizations on 32 bit but not on 64 bit. Current upstream r600g refuses to
> build without LLVM, so this should clear up on its own at some point. Maybe you
> can try current oneiric live CDs.

Yes, LLVM support is increased FPS in amd64 and drop it in i386.

[André Oliva (gandreoliva)]

I confirm that Gnome 3 hangs in Fedora 15. I booted from a live USB.

I could start Unity 3D, but someone could start Gnome 3? And how?

[Phil Cole (filcole)]

Still occurs on Fedora 16 test day live CD ISO.
https://fedoraproject.org/wiki/Test_Day:2011-09-07_Radeon
http://adamwill.fedorapeople.org/graphics_test_week_20110905/graphics_test_week-20110905-i686.iso

[Adam Williamson (awilliamson)]

So it seems the bug got a bit sidetracked by that speed issue, but regardless of that, the underlying issue doesn't seem to have been addressed: both reporters seem to need the 'noapic' or 'irqpoll' workarounds to get things flying at all. Is anything happening to address the fundamental bug?

[André Oliva (gandreoliva)]

(In reply to comment #53)
> So it seems the bug got a bit sidetracked by that speed issue, but regardless
> of that, the underlying issue doesn't seem to have been addressed: both
> reporters seem to need the 'noapic' or 'irqpoll' workarounds to get things
> flying at all. Is anything happening to address the fundamental bug?

When I tried Fedora 15 from Live USB, I could *not* start Gnome 3 (--> bad 3d acceleration --> the same bug) [blank screen and the pinter]. I used uNetbootin to create the Live USB, and even if I tried to add "noapic" to the boot line, it didn't work. Also I tried killing the X server, running "export vblank_mode=0" and "export CLUTTER_VBLANK=none" and restarting X server and also didn't work. Of course, I didn't tried installing Fedora 15, and then retrying the workaround, but at least from Live USB I couldn't make it work.

However, I noticed that when Gnome 3 loads and the freeze happens, and then I press ALT+F2, kill gnome-shell, and then ALT+F8, the Gnome-shell elements (top panel and dash) appear in the screen, but of course I can not use it because I killed the process. It's may be a clue.

[agd5f (agd5f)]

(In reply to comment #54)
> However, I noticed that when Gnome 3 loads and the freeze happens, and then I
> press ALT+F2, kill gnome-shell, and then ALT+F8, the Gnome-shell elements (top
> panel and dash) appear in the screen, but of course I can not use it because I
> killed the process. It's may be a clue.

Interrupts aren't working on your system for some reason. That's the issue. The "freeze" is gnome shell waiting for an event that never comes because interrupts aren't working.

[Phil Cole (filcole)]

(In reply to comment #55)
>
> Interrupts aren't working on your system for some reason. That's the issue.
> The "freeze" is gnome shell waiting for an event that never comes because
> interrupts aren't working.

How can I help debug this issue?? I am willing to investigate into any areas that you think may be causing this - I may need some help, e.g. bisect instructions, knowing which versions to try, etc.

p.s. Win7 works OK on the laptop, and does HW accelerated Aero mode.

[agd5f (agd5f)]

(In reply to comment #56)
>
> How can I help debug this issue?? I am willing to investigate into any areas
> that you think may be causing this - I may need some help, e.g. bisect
> instructions, knowing which versions to try, etc.
>
> p.s. Win7 works OK on the laptop, and does HW accelerated Aero mode.

Presumably the system bios on your board is not setting up the northbridge correctly. You might see if there is a new system bios for your board. It would be interesting to find out if windows has working irqs on your board. We don't currently have a fallback path in the open source driver if irqs aren't working and for certain things it's nearly impossible without irqs. You might also try the noapic or irqpoll kernel options. Additionally, if KMS was working with an older kernel, it would be great if you could bisect.

[André Oliva (gandreoliva)]

I don't think that is the Bios. I have 3 OS on 3 partitions: Windows XP,
Ubuntu 10.04 LTS and Ubuntu 11.04. 3d acc works well on Windows and Ubuntu
10.04. It doesn't work in Ubuntu 11.04.

El 09/09/2011 16:31, <email address hidden> escribió:

https://bugs.freedesktop.org/show_bug.cgi?id=37679
--- Comment #57 from Alex Deucher <email address hidden> 2011-09-09 15:31:17 PDT
---
(In reply to comment #56)

>
> How can I help debug this issue?? I am willing to investigate into any
areas
> that you think m...
Presumably the system bios on your board is not setting up the northbridge
correctly. You might see if there is a new system bios for your board. It
would be interesting to find out if windows has working irqs on your board.
 We
don't currently have a fallback path in the open source driver if irqs
aren't
working and for certain things it's nearly impossible without irqs. You
might
also try the noapic or irqpoll kernel options. Additionally, if KMS was
working with an older kernel, it would be great if you could bisect.

[agd5f (agd5f)]

(In reply to comment #58)
> I don't think that is the Bios. I have 3 OS on 3 partitions: Windows XP,
> Ubuntu 10.04 LTS and Ubuntu 11.04. 3d acc works well on Windows and Ubuntu
> 10.04. It doesn't work in Ubuntu 11.04.

As I mentioned previously, it depends if 10.04 used KMS or UMS. UMS did not make as extensive use of interrupts as KMS does. If 10.04 used KMS, then please bisect the kernel to see what commit caused the problem.

[André Oliva (gandreoliva)]

(In reply to comment #59)
> (In reply to comment #58)
> > I don't think that is the Bios. I have 3 OS on 3 partitions: Windows XP,
> > Ubuntu 10.04 LTS and Ubuntu 11.04. 3d acc works well on Windows and Ubuntu
> > 10.04. It doesn't work in Ubuntu 11.04.
>
> As I mentioned previously, it depends if 10.04 used KMS or UMS. UMS did not
> make as extensive use of interrupts as KMS does. If 10.04 used KMS, then
> please bisect the kernel to see what commit caused the problem.

Based on here
https://help.ubuntu.com/community/RadeonDriver and the release notes of Lucid,
I guess that 10.04 used KMS, not UMS.

I have 10.04 still installed in my laptop. Is there a way to check if KMS is been used?

And if so, I'm completely unfamiliar with bisecting the kernel. Could you please give me more instructions about what does it mean and how to do it?

[André Oliva (gandreoliva)]

@Muhammet Aklan:

If
export vblank_mode=0
glxgears

didn't worked, perhaps it's another bug... Please check it that works (you must see the gears).

----------------------
Update (from the freedesktop-bugs 37679):
This bug is caused by interrupts. They're not working. The solution for this problem is:
- To see if Ubuntu 10.04 (where all things worked well) used UMS instead of KMS.
- If Lucid used KMS, to bisect the kernel to see what change caused the problem.

[oxalis (oxalis)]

Hi. I'm having this bug. I'm using Gentoo, not Ubuntu.

If kms is in use, Xorg.0.log has the following line:
  [ 1776.086] (II) [KMS] Kernel modesetting enabled.

Very good git bisect tutorial is found here:
http://www.landley.net/writing/git-bisect-howto.html

I may add some more comments after some investigation.

With best regards.

[agd5f (agd5f)]

Older versions of radeon kms did not support vsynced 3D which relies on vblank interrupts in addition to sw interrupts. You can disable it by setting the env var vblank_mode=0.

[oxalis (oxalis)]

Hi. I noticed one peculiar thing: IRQ 19 (radeon's) is almost always frozen at 200001 times:
 $ cat /proc/interrupts
           CPU0
  0: 409332 IO-APIC-edge timer
  1: 448 IO-APIC-edge i8042
  8: 0 IO-APIC-edge rtc0
  9: 178 IO-APIC-fasteoi acpi
 12: 73159 IO-APIC-edge i8042
 16: 22757 IO-APIC-fasteoi ahci, hda_intel
 17: 9173 IO-APIC-fasteoi ohci_hcd:usb3, ohci_hcd:usb4, ohci_hcd:usb5, ohci_hcd:usb6
 19: 200001 IO-APIC-fasteoi radeon
 23: 2 IO-APIC-fasteoi ehci_hcd:usb1, ohci_hcd:usb2
 42: 30400 PCI-MSI-edge eth0
NMI: 0 Non-maskable interrupts
LOC: 173250 Local timer interrupts
SPU: 0 Spurious interrupts
PMI: 0 Performance monitoring interrupts
IWI: 0 IRQ work interrupts
ERR: 0
MIS: 0

And it seems when it reaches that number, dmesg "irq 19: nobody cared" appears, though not sure.

I've also seen the number 300001, only once during several rebooting. Except this time, all was 200001. Why step of 100000??

But Phil Cole said above that he has 2 cpus, and the threshold of the attachement[1] was 281.
[1]https://bugs.freedesktop.org/attachment.cgi?id=47380

"noapic" boot option doesn't help. I tried it only once, and it showed:
11: 200002 XT-PIC-XT-PIC ehci_hcd:usb1, ohci_hcd:usb2, radeon

(Without noapic, the ERR interrupt is always 0, but with noapic, ERR increases.)

Let me add one more issue, module vs built-in: when I compile the driver "radeon" as a module, kms starts. But if it's built into the kernel, it freezes at the boot time, showing black screen. Keyboard is ignored, and HDD access LED doesn't turn on. I've checked it's the only difference. (In menuconfig, CONFIG_DRM_RADEON being "m" or "y". In the .config file this option will automatically pull in several other flags.)

I tried boot options below, but none worked: "irqpoll", "ioapicreroute", "nohz=off processor.max_cstate=2". (In the past, the last one was necessary for my HP Compaq 6715s, but recent kernels do't require it.)

[oxalis (oxalis)]

I found several other "200001" IRQ issues, completely independent of radeon:

* Wireless driver, with a successful fix. (Too bad kernel.org is closed now, but if you have kernel git repo on your local HDD, the relevant commit is shown.)
https://bugzilla.redhat.com/show_bug.cgi?id=537943

All others shown below don't contain fix.

* nvidia
http://www.linuxquestions.org/questions/slackware-14/disabling-irq-16-a-879964/

* Ata?
http://www.amailbox.org/mailarchive/linux-kernel/2007/8/26/164946/thread#mid-164946

* ether card
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/126369

* ehci_usb
http://answers.softpicks.net/answers/topic/USB-Serial-device-disconnect-causes-IRQ-disable-1978236-1.htm

You can also find 100001 and 300001 cases. Is there any nasty kernel or acpi spec bug?

Thanks in advance.

[Michel Dänzer (michel-daenzer)]

(In reply to comment #64)
> I found several other "200001" IRQ issues, completely independent of radeon:

That's a red herring I'm afraid: If you look at the code in kernel/irq/spurious.c, this message is generated after 200000 unhandled interrupts, and then the IRQ is disabled. The 100001 and 300001 values probably have the same explanation with different kernel versions or patched kernels.

Unfortunately, this doesn't say anything about what caused the interrupts not to be handled properly in each case.

[oxalis (oxalis)]

Hi. With kernel-3.0.4, the problem seems to be gone for me.

And thank you, Michel Dänzer, for your comment.

[agd5f (agd5f)]

(In reply to comment #66)
> Hi. With kernel-3.0.4, the problem seems to be gone for me.

Any chance you could bisect and track down what commit fixed it?

[oxalis (oxalis)]

Sorry, I was wrong. No difference between 2.6.39.2 and 3.0.4.

OTOH, I tried 2.6.32.36, and kms worked, although "EnablePageFlip" "off" was necessary; without it, the screen is black, showing nothing. vblank_mode=0 doesn't affect fps of glxgears.

Below I've attached dmesg of 2.6.32.36 (good) and 3.0.4 (bad).

You'll have noticed both have a line
  radeon 0000:01:05.0: PCI INT B -> GSI 19 (level, low) -> IRQ 19
but in the good, there's also a line
  radeon 0000:01:05.0: irq 26 for MSI/MSI-X
and /proc/interrupts says only irq # 26 is used in the good. (In bad, it's 19.)

[oxalis (oxalis)]

Created attachment 52414
dmesg of 2.6.32.36

[oxalis (oxalis)]

Created attachment 52415
dmesg of 3.0.4

[oxalis (oxalis)]

Created attachment 52416
dmesg of 2.6.32.36 (radeon part only)

[oxalis (oxalis)]

Created attachment 52417
dmesg of 3.0.4 (radeon part only)

[oxalis (oxalis)]

Created attachment 52418
cat /proc/interrupts from 2.6.32

[oxalis (oxalis)]

Created attachment 52419
glxinfo from 2.6.32

[Muhammet Aklan (aklan)]

@André Oliva,

Thanks for the answer. I'm currently using 10.04 with Linux kernel 3.0.0.12, which is backported from Oneiric (from Ubuntu kernel team's PPA). So I'm sure that what causes the bug isn't the difference between kernel versions.

I'm booting Lucid with "nomodeset" option, because it runs too slow when I don't use that option. However, on Oneiric, that option causes lack of support for Unity 3D. Without using it, Compiz doesn't start, so both Unity's and GNOME's 3D versions cannot be started although it seems that Unity 3D support is available.

I think the best solution for this problem is returning to LTS for now. I hope the bug will be solved soon.

[agd5f (agd5f)]

Does 2.6.32.36 work correctly if you boot with pci=nomsi on the kernel command line in grub? How about 3.0.4?

[oxalis (oxalis)]

2.6.32 with pci=nomsi:

It's "bad". irq # 19 count is frozen. glxgears draws, but the FPS is reduced 70, while without "nomsi" it was 240. Xorg log is the same. dmesg is same except "irq for nomsi".

I haven't reported this before, but when it's "bad", redraw of my x terminal, urxvt, is snail-slow, and I saw it with "nomsi", too. (I don't need opengl, so this is the biggest trouble for me.)

3.0.4: no much difference with pci=nomsi, it's anyway bad. (In 2.6.39 and 3.0.4, in most cases glxgears is not drawn, showing only black box. But in 2.6.32, every time I tried gears were drawn even with nomsi, but the test is not thorough.)

Most of dmesg differences are trivial, but I quote one hunk here FYI:
------------------------------------------------------------------------
--- dmesg-3.0.4 2011-10-18 17:02:54.743566206 +0900
+++ dmesg-3.0.4-nomsi 2011-10-18 16:57:38.871537255 +0900
@@ -268,9 +266,7 @@
 ACPI: PCI Interrupt Routing Table [\_SB_.C08B._PRT]
 ACPI: PCI Interrupt Routing Table [\_SB_.C08B.C08C._PRT]
 ACPI: PCI Interrupt Routing Table [\_SB_.C08B.C0FC._PRT]
- pci0000:00: Requesting ACPI _OSC control (0x1d)
- pci0000:00: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d
-ACPI _OSC control for PCIe not granted, disabling ASPM
+ pci0000:00: Unable to request _OSC control (_OSC support mask: 0x0f)
 ACPI: PCI Interrupt Link [C145] (IRQs 10 11) *0, disabled.
 ACPI: PCI Interrupt Link [C146] (IRQs 10 11) *0, disabled.
 ACPI: PCI Interrupt Link [C147] (IRQs 10 11) *0, disabled.
------------------------------------------------------------------------

[agd5f (agd5f)]

Created attachment 52475
enable msi

Looks like only MSIs work on your system. Does the attached patch fix newer kernels?

[oxalis (oxalis)]

I patched 3.0.4. It's a must-have, but not simple.

It partially fixes. "black box glxgears" nor "irq count freeze" never happen. "pageflip" on-or-off doesn't matter. Xorg.0.log isn't affected. dmesg is the same with unpatched 3.0.4, except MSI:
------------------------------------------------------------------------
@@ -8,12 +8,10 @@
 radeon 0000:01:05.0: GTT: 512M 0x0000000060000000 - 0x000000007FFFFFFF
 [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
 [drm] Driver supports precise vblank timestamp query.
+radeon 0000:01:05.0: irq 42 for MSI/MSI-X
+radeon 0000:01:05.0: radeon: using MSI.
 [drm] radeon: irq initialized.
 [drm] Detected VRAM RAM=128M, BAR=128M
 [drm] RAM width 128bits DDR
------------------------------------------------------------------------

Glxgears fps is always only 60 (which is 240 with good kms), regardless of "pageflip" or "vblank_mode=0".

But that's not all; The first time I booted the patched kenel, right after udev loaded the module, (I was on VT1) it seemed ok - the screen went high resolution, the previous screen contents were correctly shown, and the cursor continued blinking - but it halted there. Keypresses are echoed to the screen, but Ctrl+Alt+Del didn't work.

It happened only once, and after that, all 5 boots were successful.

It also seems to have a nice side effect; when kms is enabled in the bad kernel, I often experinced a problem in s2ram, but with your patch s2ram has succeeded in some 10 trials in row. So I think we're in the right direction.
(The problem was that for most times suspend doesn't complete, or takes too long, after the screen turns black.)

Since I don't need opengl, I'm quite satisfied with this patch. =P

[agd5f (agd5f)]

What are your pci device and subsystem ids? lspci -vnn

[oxalis (oxalis)]

Created attachment 52722
lspci -vnn of katabami's PC

In short, same as Phil Cole's:

01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS690M [Radeon X1200 Series] [1002:791f] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:30c2]

Thank you very much for taking care.
With kind regards.

[agd5f (agd5f)]

Created attachment 52758
fix 1/2

Patch 1/2

[agd5f (agd5f)]

Created attachment 52759
fix 2/2

patch 2/2

Can you try these two patches? It looks like a platform/bios bug rather than a driver bug since legacy irqs should always work AFAIK, but I'm not sure where the problem lies. This patch just adds a quirk to always enable MSIs on your system.

[oxalis (oxalis)]

Thanks, it surely works, again for 3.0.4.

I forgot to report that built-in driver (= not as modules) doesn't work with 2.6.32, nor with 3.0.4 + your patch.

If someone wants to bisect: it'll take some 18-20 times of kernel compilation, I guess. I've done kernel bisect twice, but both were straightforward. As usual, you can ask helps at forums. You can also ask me by email for basic procedures. (Login here to see my email address.)

[agd5f (agd5f)]

(In reply to comment #83)
> Thanks, it surely works, again for 3.0.4.
>
> I forgot to report that built-in driver (= not as modules) doesn't work with
> 2.6.32, nor with 3.0.4 + your patch.

Did you include the required firmware in your kernel image?

[agd5f (agd5f)]

Can anyone else on this report check if attachment 52475 helps you as well?

[oxalis (oxalis)]

(In reply to comment #84)
Thanks again. Built-in works just like module by adding the firmware, radeon/RS690_cp.bin, for each version.

# Oh my ass, I've never heard of that magic. ;)

[oxalis (oxalis)]

Created attachment 52873
Xorg.0.log from 2.6.32

Some notes on glxgears FPS: 2.6.32 reports more resolution modes, and fps varies among modes. In 3.0.4 + patch, fps is about 60 in all modes.

Let me attach Xorg server's logs. This file is from 2.6.32.

[oxalis (oxalis)]

Created attachment 52874
Xorg.0.log from 3.0.4

Xorg.0.log from 3.0.4

[Phil Cole (filcole)]

Just completed a fresh install of Fedora 15 x86 and rebuilt the stock Fedora kernel (2.6.40.6) keeping the exact same configuration apart from the addition of the two patches from Comment 81 and Comment 82 and it fixes the problem as far as I can see.

Boots fine without kernel param "nomodeset".
glxgears gives approx 57-60fps.
Gnome3 much more responsive.

Thanks Alex for your persistence with this bug. Thanks katabami too.

[André Oliva (gandreoliva)]

I, the original reporter of this bug, want to thank also Alex and all the
people involved for all the effort and the time spent in this bug. These
weeks I simply didn't have enough time to try to bisect the Kernel and to
try the patches (I'm unfamiliar with that and it's something that I have to
learn how to do it). Sorry for that. But really, thank you very much!

2011/10/29 <email address hidden>

> https://bugs.freedesktop.org/show_bug.cgi?id=37679
>
> --- Comment #89 from Phil Cole <email address hidden> 2011-10-29 12:09:28 UTC
> ---
> Just completed a fresh install of Fedora 15 x86 and rebuilt the stock
> Fedora
> kernel (2.6.40.6) keeping the exact same configuration apart from the
> addition
> of the two patches from Comment 81 and Comment 82 and it fixes the problem
> as
> far as I can see.
>
> Boots fine without kernel param "nomodeset".
> glxgears gives approx 57-60fps.
> Gnome3 much more responsive.
>
> Thanks Alex for your persistence with this bug. Thanks katabami too.
>
> --
> Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>

[André Oliva (gandreoliva)]

There is a patch in freedesktop.org bug tracker, that seems to fix the problem. If someone wants to try it, it's there, but please be careful.

[Ian McMichael (ian-sigma-uk)]

The performance of my HP Compaq 6715b with an RS690M has regressed so badly in Oneiric that I've been forced into action. Based on the work done in Bug #874784 and the patches provided by Alex Deucher in https://bugs.freedesktop.org/show_bug.cgi?id=37679 I have built my first kernel. It builds on 3.0.0-13-generic #22 from the Oneiric Proposed repository and I have only built the i386, which is what I run.

I have attached a copy of the new kernel I am running, which restored the 3D acceleration on my hardware. It would be great if others could test and then we could work out a way to get these patches incorporated into the next kernel release for Oneiric.

[Ian McMichael (ian-sigma-uk)]

Generic headers for the above kernel

[Ian McMichael (ian-sigma-uk)]

i386 headers for above kernel

[Dennis Fehr (cy-raid)]

Good job Ian! I hope more people can test Ian's patch and see if it works for them. We all want a smooth Oneiric experience and not to scare anyone away from using it because of some silly bug!

[Muhammet Aklan (aklan)]

Hello again.

Is installing the kernel packages whose links above enough to solve the problem? If so, unfortunately this solution doesn't work for ATI Radeon X550. If it is not enough, would you mind telling me other things I must do? Because I can't describe myself as an expert.

Thanks to everyone in advance for their work and possible answers.

[Ian McMichael (ian-sigma-uk)]

No, as far as I can see from the code modifications AMD made in the patches this will only fix the RS690M. In terms of installing my test kernel, I have a vanilla Oneiric i386 desktop installation and then ran "dpkg -i" on each of the three .deb files I created in turn. After a reboot things improved considerably.

[André Oliva (gandreoliva)]

@Muhammet Aklan: I recommend you to file a bug in freedesktop.org, just as I did. In order to be sucessful, I recommend you to be very clear and summarize the symptoms, hardware, version of the kernel, what works, what doesn't work, what have you tested, etc., etc., etc. very very well, and, of course, try to link to the bug I filed in freedesktop.org. Be patient, but a clean bug report is more likely to be quickly fixed.

It can be helpful to file a bug also here in Launchpad, specific for Radeon X550, so other Ubuntu users with that model can help you with the bug report on freedesktop.

[Leonardo Brás (leonardobsp)]

Since i use AMD64 and i use to build my own kernel, where can i find that patches done by AMD?

Thank you

Leonardo Brás

Em 07/11/2011, às 07:31, Ian McMichael <email address hidden> escreveu:

> No, as far as I can see from the code modifications AMD made in the
> patches this will only fix the RS690M. In terms of installing my test
> kernel, I have a vanilla Oneiric i386 desktop installation and then ran
> "dpkg -i" on each of the three .deb files I created in turn. After a
> reboot things improved considerably.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (874784).
> https://bugs.launchpad.net/bugs/755791
>
> Title:
> [RS690M] No 3d acceleration in Radeon X1200 with new Gallium r300 / 3d
> drivers in 11.04
>
> Status in The Linux Kernel:
> Fix Committed
> Status in X.org XServer - ATI gfx chipset driver:
> Fix Committed
> Status in “xserver-xorg-video-ati” package in Ubuntu:
> Confirmed
> Status in Fedora:
> Unknown
>
> Bug description:
> The bug is active also in Freedesktop.org :
> https://bugs.freedesktop.org/show_bug.cgi?id=37679
>
> [edit]
> The bug seems to be fixed with a patch provided by Freedesktop.org team.
> [/edit]
>
> [edit]
> This bug is caused by interrupts. They're not working. The solution for this problem is:
> - To see if Ubuntu 10.04 (where all things worked well) used UMS instead of KMS.
> - If Lucid used KMS, to bisect the kernel to see what change caused the problem.
>
> [/edit]
>
> [edit]
> The bug description, updated:
>
> The symptoms: No 3d acceleration (glxgears shows a black window, Unity
> doesn't start), *but* no fallback into the software-rendering mode
> (glxinfo reports that the 3d acceleration is working)
>
> The hardware: ATI Radeon RS690M X1200 series
>
> The version of Ubuntu: Ubuntu 11.04 (final release) [and Maverick
> also]. The behavior was also observed in Debian and Fedora 15, as
> noted below (so it seems not to be Ubuntu-specific).
>
> The version of xserver-xorg-video-ati: 1:6.14.0-0ubuntu4 (default in
> Natty). Same problems with the xorg-edgers PPA in Natty Beta2.
>
> The software affected: Compiz (doesn't start because requires direct
> rendering); then, Unity (just the wallpaper or black screen and the
> mouse pointer). glxgears, Stellarium, Blender, Adobe Flash Player in
> fullscreen mode and Visual module of Python work if software rendering
> is forced (but of course they run very very slow).
>
> The history of the bug: all worked as expected (out of the box) in
> 10.04, but in 10.10 the problems started. The workaround was to
> disable KMS, but now, in Maverick, since the new Gallium driver
> doesn't have a non-KMS mode, that workaround is not available. This
> issue was reported when using 11.04 Beta 1 and Beta 2, then, in the
> descriptions below there are some strange things (xorg crash during
> startup, software rendering fallback), that don't occur any more. The
> issue is just the description given here.
>
> The exceptions: **sometimes** (??) the 3d acceleration does work as
> expected, but at the moment there is no way for us to know when it
> will work or n...

[Ian McMichael (ian-sigma-uk)]

Patches in https://bugs.freedesktop.org/show_bug.cgi?id=37679 (posts 81 and 82) by Alex Deucher. Please report back how you get on as I'm keen to get Canonical to adopt this into the Oneiric kernel as it is a bad regression.

[Dennis Fehr (cy-raid)]

Hmmm.. On deeper investigation, my issue still remains. (I'm on nvidia) .. The desktop eventually just lags on it's own, it was the reboot that made it faster. Although when I disabled Wobbly Windows, it ran fast again.. Thinking possibly it's a bug in Wobbly Windows..?

[André Oliva (gandreoliva)]

@Dennis: are you using nvidia? This is an ATI X1200 specific bug...

2011/11/10 Dennis Fehr <email address hidden>

> Hmmm.. On deeper investigation, my issue still remains. (I'm on nvidia)
> .. The desktop eventually just lags on it's own, it was the reboot that
> made it faster. Although when I disabled Wobbly Windows, it ran fast
> again.. Thinking possibly it's a bug in Wobbly Windows..?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/755791
>
> Title:
> [RS690M] No 3d acceleration in Radeon X1200 with new Gallium r300 / 3d
> drivers in 11.04
>
> Status in The Linux Kernel:
> Fix Committed
> Status in X.org XServer - ATI gfx chipset driver:
> Fix Committed
> Status in “xserver-xorg-video-ati” package in Ubuntu:
> Confirmed
> Status in Fedora:
> Unknown
>
> Bug description:
> The bug is active also in Freedesktop.org :
> https://bugs.freedesktop.org/show_bug.cgi?id=37679
>
> [edit]
> The bug seems to be fixed with a patch provided by Freedesktop.org team.
> [/edit]
>
> [edit]
> This bug is caused by interrupts. They're not working. The solution for
> this problem is:
> - To see if Ubuntu 10.04 (where all things worked well) used UMS instead
> of KMS.
> - If Lucid used KMS, to bisect the kernel to see what change caused the
> problem.
>
> [/edit]
>
> [edit]
> The bug description, updated:
>
> The symptoms: No 3d acceleration (glxgears shows a black window, Unity
> doesn't start), *but* no fallback into the software-rendering mode
> (glxinfo reports that the 3d acceleration is working)
>
> The hardware: ATI Radeon RS690M X1200 series
>
> The version of Ubuntu: Ubuntu 11.04 (final release) [and Maverick
> also]. The behavior was also observed in Debian and Fedora 15, as
> noted below (so it seems not to be Ubuntu-specific).
>
> The version of xserver-xorg-video-ati: 1:6.14.0-0ubuntu4 (default in
> Natty). Same problems with the xorg-edgers PPA in Natty Beta2.
>
> The software affected: Compiz (doesn't start because requires direct
> rendering); then, Unity (just the wallpaper or black screen and the
> mouse pointer). glxgears, Stellarium, Blender, Adobe Flash Player in
> fullscreen mode and Visual module of Python work if software rendering
> is forced (but of course they run very very slow).
>
> The history of the bug: all worked as expected (out of the box) in
> 10.04, but in 10.10 the problems started. The workaround was to
> disable KMS, but now, in Maverick, since the new Gallium driver
> doesn't have a non-KMS mode, that workaround is not available. This
> issue was reported when using 11.04 Beta 1 and Beta 2, then, in the
> descriptions below there are some strange things (xorg crash during
> startup, software rendering fallback), that don't occur any more. The
> issue is just the description given here.
>
> The exceptions: **sometimes** (??) the 3d acceleration does work as
> expected, but at the moment there is no way for us to know when it
> will work or not [help please!]. And, sometimes the 3d acceleration
> work but is so slow that it seems to be actually software rendering.
>
> The workarounds: `vblank...

[Dennis Fehr (cy-raid)]

I'm not too sure the other bug report made duplicate to this one (bug #874784) is the same bug. The other link led me to here first so I replied here in error. I meant to reply to bug #874784. Bug #874784 seems more like bug #764330 (Move window annoying slow with compiz) instead of this issue.

[oxalis (oxalis)]

I hope it's ok for me to say, but Alex Deucher has kindly commited the patches 10 days ago, and the fix seems available in 3.0.9 and 3.1.1.

Let me express my gratitude to Alex, and all involved people. If André and Phil didn't report it, I was clueless. :)

With best regards.

[oxalis (oxalis)]

Folks, when you try the patch in the freedesktop bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=37679
be sure to use the patch titled "enable.msi" unless your PC is HP and has RS690M.
The patch has to applied to kernels < 3.0.9 or 3.1.0, or it may be rejected.

[Bryce Harrington (bryce)]

Looks like upstream has identified some kernel patches; the patches need to be escalated to the Ubuntu kernel team.

[Ian McMichael (ian-sigma-uk)]

Having upgraded to the 3.0.0-13-generic #22-Ubuntu kernel (without the RS690M patch) after the security release a couple of days ago, I realise that there is really no improvement on my HP Compaq 6715b whether I run Alex's patch or not. The graphics are very lagged in both Unity 3D and 2D.

For an example of this, pull down the far-right (what is the name for that, settings?) from the top bar and move your mouse pointer up and down over the menu items. The orange highlight bar lags substantially behind the mouse pointer position. The same can be observed by picking a window up by its title bar and dragging it around the workspace. The mouse pointer becomes more and more detached from the title bar of the window as you drag and the window lags behind.

Hopefully this explains the usability impact of this bug? If there's any more technical data I can collect from my particular RS690M installation that would help, please just ask?

[Ian McMichael (ian-sigma-uk)]

OK, I spoke too early in my last post. The machine was working fine all day Thursday with the official 3.0.0-13-generic kernel. Then when I booted it on Friday morning, lightdm displayed fine but the UI froze logging into any account with a background bitmap and mouse cursor. Unity did not display, and apart from using CTRL+ALT+F1 to switch to another console, the GUI was completely unusable.

Thinking I may have an ecryptfs issue, I booted off a USB stick with the live Oneric i386 image on it. This gave the same error. I removed the hard disk from the machine and tried again to completely remove any existing configuration or broken file-system causes. The result was the same, the GUI froze.

Next I downloaded a Natty i386 CD image and put this on the flash drive. This release had never caused me any issues on the HP Compaq 6715b. However, this now caused the same GUI freeze trying to launch Unity.

Eventually, I went back to the Lucid LTS i386 image with Gnome and everything booted fine and I was able to use the GUI from the flash drive. I used this UI to download the patched kernel I have posted in this bug and copied it back to my system. I booted back into the hard-drive installation, switched to console 1 with CTRL+ALT+F1 and used dpkg to re-install my 3.0.0.13 kernel with the AMD patches. After a reboot I was again able to log in and the Unity interface displays again. However, the horrific lagging and general lack of usability of the interface on this machine remain.

Does the RS690M have some sort of firmware the kernel can corrupt? The Canonical 3.0.0-13-generic kernel is the first time on this particular machine I have ever had a complete show-stopper bug where the UI fails to display. (This is after running Natty for 6 months on the same machine previously!) I now believe we may have two bugs here. One that corrupts the firmware in some way and actually stops the RS690M working on these machines, and another (maybe Compiz) that causes the horrendous lag and lack of usability.

What do others experiencing these issues think?

[W-florijn-k (w-florijn-k)]

A patch referencing this bug report has been merged in Linux v3.2-rc1:

commit b362105f7f5223fa4d2e03ceeea0e51da754ccc6
Author: Alex Deucher <email address hidden>
Date: Tue Oct 25 15:11:08 2011 -0400

    drm/radeon/kms: Add MSI quirk for HP RS690

[W-florijn-k (w-florijn-k)]

A patch referencing this bug report has been merged in Linux v3.2-rc1:

commit a18cee15ed4c8b6a35f96b7b26a46bac32e04bd9
Author: Alex Deucher <email address hidden>
Date: Tue Nov 1 14:20:30 2011 -0400

    drm/radeon/kms: add MSI module parameter

[Pasis-uax (pasis-uax)]

I have the same problem with my DELL Inspiron 1521 laptop and the patch doesn't fix the problem cause my video card reports another subsystem_device:
cat /sys/bus/pci/devices/0000:01:05.0/subsystem_device
0x01fc

So I just changed subsystem_device in the patch and now it works fine.

[agd5f (agd5f)]

Created attachment 55596
Add another DELL quirk

I've sent this additional patch upstream.

[W-florijn-k (w-florijn-k)]

A patch referencing this bug report has been merged in Linux v3.2-rc1:

commit 01e718ec194e30b3e8eb3858c742c13649757efc
Author: Alex Deucher <email address hidden>
Date: Tue Nov 1 14:14:18 2011 -0400

    drm/radeon/kms: Add MSI quirk for Dell RS690

[W-florijn-k (w-florijn-k)]

A patch referencing this bug report has been merged in Linux v3.3-rc2:

commit 44517c44496062180a6376cc704b33129441ce60
Author: Alex Deucher <email address hidden>
Date: Sun Jan 15 08:51:12 2012 -0500

    drm/radeon/kms: Add an MSI quirk for Dell RS690

[Agent24 (tda7000)]

I have this problem with my Radeon 9600XT

I had this problem on an install of Ubuntu Natty and so far the only thing I can confirm with repeatability is that 3D works when the S-video output is 'detected' and doesn't work when it isn't.

If I boot into Windows XP (dual boot) and enable the TV-Out on S-Video (even without a TV plugged in) and then reboot into Ubuntu Natty I get a 2nd screen on S-video showing up in the displays control panel and I get 3D acceleration to work.

I installed a test copy of Ubuntu Oneiric onto a USB HDD and so far haven't had issues with 3D.

HOWEVER: I recently did an upgrade to Oneiric inside the currently-installed Natty and the 3D issue is still present, so perhaps that is from something still there from the old installation?

Again, enabling S-video in Windows and rebooting is the only sure way to make 3D work.

Occasionally it will boot up and detect the S-video and enable 3D by itself but this is not often.

[Michel Dänzer (michel-daenzer)]

(In reply to comment #98)
> I have this problem with my Radeon 9600XT

No, you probably don't. This problem is (was? Looks like this report can be resolved now?) specific to RS690 chipsets.

Please file your own report with the usual information attached, i.e. at least Xorg.0.log and the output of dmesg and glxinfo from when the problem occurs (and maybe also from when it doesn't). Please also describe in more detail what exactly "3D acceleration doesn't work" means in your case.

[Leonardo Brás (leonardobsp)]

It the bug was gone in Precise beta1.

[krmolot (krmolot)]

Hello. Plz tell me, where i can find detailed information about my Radeon x1250. Something like this:
if ((rdev->pdev->device == 0x791f) &&
(rdev->pdev->subsystem_vendor == 0x1028) &&
(rdev->pdev->subsystem_device == 0x01fc))
Simple hack "return true;" work.
Notebook: Emachines D620
Thanks.
00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] nee ATI RS690 Host Bridge [1002:7910]
 Subsystem: Gateway 2000 Device [107b:0185]
 Flags: bus master, 66MHz, medium devsel, latency 64
 Kernel modules: ati-agp

00:01.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI RS690 PCI to PCI Bridge (Internal gfx) [1002:7912] (prog-if 00 [Normal decode])
 Flags: bus master, 66MHz, medium devsel, latency 64
 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
 I/O behind bridge: 00009000-00009fff
 Memory behind bridge: f0000000-f01fffff
 Prefetchable memory behind bridge: 00000000d0000000-00000000dfffffff
 Capabilities: <access denied>
 Kernel modules: shpchp

00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI Device [1002:7914] (prog-if 00 [Normal decode])
 Flags: bus master, fast devsel, latency 0
 Bus: primary=00, secondary=02, subordinate=04, sec-latency=0
 I/O behind bridge: 0000a000-0000afff
 Memory behind bridge: f0200000-f02fffff
 Capabilities: <access denied>
 Kernel driver in use: pcieport
 Kernel modules: shpchp

00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI RS690 PCI to PCI Bridge (PCI Express Port 1) [1002:7915] (prog-if 00 [Normal decode])
 Flags: bus master, fast devsel, latency 0
 Bus: primary=00, secondary=05, subordinate=07, sec-latency=0
 Memory behind bridge: f0300000-f03fffff
 Capabilities: <access denied>
 Kernel driver in use: pcieport
 Kernel modules: shpchp

00:12.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee ATI SB600 Non-Raid-5 SATA [1002:4380] (prog-if 01 [AHCI 1.0])
 Subsystem: Gateway 2000 Device [107b:0185]
 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 22
 I/O ports at 8440 [size=8]
 I/O ports at 8434 [size=4]
 I/O ports at 8438 [size=8]
 I/O ports at 8430 [size=4]
 I/O ports at 8400 [size=16]
 Memory at f0609000 (32-bit, non-prefetchable) [size=1K]
 Capabilities: <access denied>
 Kernel driver in use: ahci

00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB600 USB (OHCI0) [1002:4387] (prog-if 10 [OHCI])
 Subsystem: Gateway 2000 Device [107b:0185]
 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
 Memory at f0404000 (32-bit, non-prefetchable) [size=4K]
 Kernel driver in use: ohci_hcd

00:13.1 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB600 USB (OHCI1) [1002:4388] (prog-if 10 [OHCI])
 Subsystem: Gateway 2000 Device [107b:0185]
 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 17
 Memory at f0405000 (32-bit, non-prefetchable) [size=4K]
 Kernel driver in use: ohci_hcd

00:13.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB600 USB (OHCI2) [1002:4389] (prog-if 10 [OHCI])
 Subsystem: Gateway 2000 Device [107b:0185]
 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 18
 Memory at f0406000 (32-bit, non-prefetchable) [size=4K]
 Kernel driver in use: ohci_hcd

00:13.3 USB controller [0c03...

[krmolot (krmolot)]

cat /sys/bus/pci/devices/0000:01:05.0/subsystem_device
0x0185

[agd5f (agd5f)]

Created attachment 67737
fix for gateway laptop

This patch should fix your gateway laptop.

[agd5f (agd5f)]

Created attachment 67738
force MSIs for all RS690s

For anyone with an RS690, try this patch and see if it helps.

[Nicolas Delvaux (malizor)]

On my Acer Emachine e625 laptop, enabling MSI seems to be an improvement.
`vblank_mode=0 glxgears` give me 690 FPS when I had 590 without MSI.

However, the desktop experience (Unity 3D) feels the same with or without it.

[krmolot (krmolot)]

(In reply to comment #102)
> Created attachment 67737 [details] [review]
> fix for gateway laptop
> This patch should fix your gateway laptop.

Yes, it's work. Can you send this patch in upstream? :)
cat /proc/interrupts
...
43: 20852 PCI-MSI-edge radeon
Thanks.

[agd5f (agd5f)]

(In reply to comment #105)

> Yes, it's work. Can you send this patch in upstream? :)

Yes, it's already queued for 3.7 and stable.

[Nicolas Delvaux (malizor)]

I forgot this about my system:
cat /sys/bus/pci/devices/0000:01:05.0/subsystem_device
0x0213

Let me know if you need something else.

[agd5f (agd5f)]

(In reply to comment #107)
> I forgot this about my system:
> cat /sys/bus/pci/devices/0000:01:05.0/subsystem_device
> 0x0213

The patch in attachment 67738 should handle your card.

[Nicolas Delvaux (malizor)]

Yes, this patch does enable MSI and so does solve most of my problems with this laptop.
Though the patch does not apply as is (at least on the Ubuntu kernel).

[Oibaf (oibaf)]

Fixed in 3.6.2 / 3.5.7 / 3.4.14 .

[Oibaf (oibaf)]

3.5.7 fixed this and is on 12.10