From: Dave Airlie <airlied@gmail.com>
To: Dave Jones <davej@redhat.com>, Dave Airlie <airlied@gmail.com>,
Andi Kleen <ak@suse.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15-git breaks Xorg on em64t
Date: Mon, 16 Jan 2006 23:11:29 +1100 [thread overview]
Message-ID: <21d7e9970601160411q6c08cd11o9db86efbb9df6f13@mail.gmail.com> (raw)
In-Reply-To: <20060116063653.GA3112@redhat.com>
> > > Another datapoint btw: I've another EM64T that works just fine.
> > > The one that fails is the only one that isn't using onboard VGA,
> > > this one has a PCIE Radeon. Given it happens when X is starting up,
> > > it could be that the X radeon driver does something special which
> > > is why others aren't seeing this.
> > >
> >
> > It might be due to the DRM update that went through, but I can't think
> > what might have caused it, if you backout the DRM merge does it help
> > any?
>
> As it turns out, -git11 with all the DRM bits backed out gives me
> a working X again.
>
> > did the previous kernel have DRM support for that card?
>
> No. This is 1002:5b60 / 1002:5b70 based card.
>
> I had previously missed the 5b60 part in lspci output, so thinking
> there was no 5b70 addition, I hadn't considered this as a suspect.
> Mea Culpa. Looks like Andi is off the hook :-)
>
> Any ideas for any debugging I can add ?
Disable dri in your xorg.conf first, (remove the Load "dri"), if that
works which it most likely will, then send me an Xorg.0.log, and a drm
debug trace (modprobe drm debug=1),
I'm going to be looking at a 64-bit machine with PCIE radeon in the
next day or two, I'll be getting one myself post LCA more than
likely...
I think more than likely we are hitting a problem where the DRM sets
up the radeon RAM controller and the X server sets it up
differently... benh has fixes for this but they need to go into the X
server driver....
Dave.
>
> Dave
>
>
next prev parent reply other threads:[~2006-01-16 12:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 6:52 Dave Jones
2006-01-14 14:49 ` Alessandro Suardi
2006-01-14 18:43 ` Andi Kleen
2006-01-14 22:51 ` Dave Jones
2006-01-15 0:05 ` Andi Kleen
2006-01-15 7:06 ` Dave Jones
2006-01-15 8:35 ` Anton Altaparmakov
2006-01-15 9:36 ` Dave Airlie
2006-01-16 6:36 ` Dave Jones
2006-01-16 12:11 ` Dave Airlie [this message]
2006-01-15 15:47 ` Andi Kleen
2006-01-16 4:29 ` Dave Jones
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=21d7e9970601160411q6c08cd11o9db86efbb9df6f13@mail.gmail.com \
--to=airlied@gmail.com \
--cc=ak@suse.de \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®