LKML Archive on
help / color / mirror / Atom feed
From: Jonathan McDowell <>
To: Dave Airlie <>
Cc: Andrew Morton <>,,
Subject: Re: 2.6.25-rc3 + RS690 + DRM + xf86-video-ati hang
Date: Tue, 4 Mar 2008 10:33:55 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, Mar 04, 2008 at 09:24:08AM +0000, Dave Airlie wrote:
> > > results in a machine that boots to GDM successfully. Likewise if I
> > > disable CONFIG_DRM_RADEON in 2.6.25-rc3 the machine boots to GDM
> > > ok.
> > 
> > is what we wanted to know, thanks.  Surely it's a plain old
> > regression?
> Nope, its a userspace driver problem.. we have not released
> non-experimental code for that chipset, so its not surprising it fails
> when the kernel code gets run, but the fix most likely is in userspace
> not in the kernel.
> I could disable the userspace DRI code but then where would I find my
> testers .. if he reads his Xorg log it says DRI is experimental on
> rs690 and not to come crying..

If you accuse your testers of coming crying when they report issues then
you'll find less of them bother coming forward. I've worked round the
problem locally by disabling the kernel DRM support and was reporting
the issue:

*) So that other people would know there was a problem and might be able
   to avoid it.


*) In case there was anything I could try out that might help to get the
   problem fixed going forward.

I understand the support for the RS690 is experimental; I'm very pleased
to see it at all in the Free xorg driver. I've also been able to ditch
the fglrx driver on my work machine (which has an X1300 running dual
head). Please don't think I'm unappreciative of your work; if I was I
wouldn't have bothered trying to improve things by reporting my issue.

(I can make the X server crash by trying to use Xv as well; I assume
there's no point in reporting that somewhere?)
> this is the problem with adding new chipsets, I either wait for 6
> months for all the bugs to get kicked out so nobody wins, or I push it
> upstream so most people win, I could back this out of the kernel, but
> experimental userspace code isn't a reason for this..

Perhaps rather than just automatically enabling the new experimental
support in the kernel there needs to be a CONFIG_DRM_RADEON_EXPERIMENTAL
option or similar to enable support for chipsets that aren't believed to
be stable?


/-\                             |  I'm from the government. I'm here
|@/  Debian GNU/Linux Developer |            to help you.
\-                              |

  reply	other threads:[~2008-03-04 10:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-01 19:35 Jonathan McDowell
2008-03-02 19:23 ` Alex Deucher
2008-03-04  6:48 ` Andrew Morton
2008-03-04  8:16   ` Dave Airlie
2008-03-04  8:51     ` Jonathan McDowell
2008-03-04  9:13       ` Andrew Morton
2008-03-04  9:24         ` Dave Airlie
2008-03-04 10:33           ` Jonathan McDowell [this message]
2008-03-04 11:23       ` Dave Airlie
2008-03-04 17:13         ` JoJo jojo
2008-03-04 18:02           ` Alex Deucher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --subject='Re: 2.6.25-rc3 + RS690 + DRM + xf86-video-ati hang' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).