From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Michael D Labriola <mlabriol@gdeb.com>
Cc: Konrad Rzeszutek Wilk <konrad@darnok.org>,
michael.d.labriola@gmail.com, xen-devel@lists.xen.org
Subject: Re: Radeon DRM dom0 issues
Date: Mon, 20 Jan 2014 10:38:27 -0500 [thread overview]
Message-ID: <20140120153827.GA24989@phenom.dumpdata.com> (raw)
In-Reply-To: <OF16949C1D.7EB315DE-ON85257C66.00540CD1-85257C66.0054D016@gdeb.com>
On Mon, Jan 20, 2014 at 10:26:22AM -0500, Michael D Labriola wrote:
> Konrad Rzeszutek Wilk <konrad@darnok.org> wrote on 01/20/2014 10:14:36 AM:
>
> > From: Konrad Rzeszutek Wilk <konrad@darnok.org>
> > To: Michael D Labriola <mlabriol@gdeb.com>,
> > Cc: xen-devel@lists.xen.org, michael.d.labriola@gmail.com
> > Date: 01/20/2014 10:14 AM
> > Subject: Re: [Xen-devel] Radeon DRM dom0 issues
> >
> > On Mon, Jan 20, 2014 at 09:58:32AM -0500, Michael D Labriola wrote:
> > > Anyone here running a dom0 w/ Radeon DRM? I'm having consistent
> crashes
> > > with multiple older R600 series (HD 6470 and HD 6570) and unusably
> slow
> > > graphics with a newer HD7000 (can see each line refresh indiviually on
>
> > > radeonfb tty). All 3 systems seem to work fine bare metal.
> >
> > I hadn't been using DRM, just Xserver. Is that what you mean?
>
> The R600 problems happen when in X, using OpenGL, on my dom0. The
> RadeonSI sluggishness is when using the KMS framebuffer device for a plain
> text console login.
So sluggish is probably due to the PAT not being enabled. This patch
should be applied:
lkml.org/lkml/2011/11/8/406
(or http://marc.info/?l=linux-kernel&m=132888833209874&w=2)
and these two reverted:
"xen/pat: Disable PAT support for now."
"xen/pat: Disable PAT using pat_enabled value."
Which is to say do:
git revert c79c49826270b8b0061b2fca840fc3f013c8a78a
git revert 8eaffa67b43e99ae581622c5133e20b0f48bcef1
>
>
> > >
> > > The R600 crashes happen seemingly randomly when using OpenGL
> Compositor in
> > > Enlightenment 0.17. My dom0 need not even have any domUs running.
> > > Sometimes it happens within a few minutes, sometimes it will run OK
> for an
> > > afternoon or so. Eventually TTM issues an "unable to get page 0"
> error
> > > message, the radeon driver follows that up with a
> > > "radeon_gem_object_create failed to allocate gem" error message. Then
> the
> > > radeon driver starts spamming that gem failure message until I'm
> forced to
> > > reboot.
> > >
> > > Behavior is identical with kernel versions 3.8, 3.10, and 3.13-rc8.
> > >
> > > I'm using Xen 4.2.1 32bit.
> > >
> > > xen command line is: vga=mode=0x314
> > > kernel command line is: root=/dev/md0 quiet pci=realloc
> > > console=ttyS0,115200n8 console=tty0
> > >
> > > Fingers crossed that there's some magic boot parameter I'm missing.
> It's
> > > been a while since I dabbled with this stuff. ;-)
> >
> > That should have been working. I had been using Xserver for years now.
> > Just to make sure - you aren't referring to running with X right? Just
> > simple framebuffer?
>
> I'm not sure I understand the delineation between Xserver and X... I am
> indeed in X, using xf86-video-ati and Mesa for OpenGL support. I've been
> doing this for years as well, but with nouveau and w/out 3d support. Was
> kinda hoping that the Radeon cards I got a hold of would allow for
> hardware accelerated 3d on my dom0.
You should be able to use 3D as well - with those said patches.
>
> I just tried adding 'nopat' to the kernel command line. I remember doing
> that a year ago... don't recall why. Any chance that helps?
Heh. So you want the inverse with a patch that fixes the PAT wreaking
havoc.
>
> ---
> Michael D Labriola
> Electric Boat
> mlabriol@gdeb.com
> 401-848-8871 (desk)
> 401-848-8513 (lab)
> 401-316-9844 (cell)
>
>
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-01-20 15:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 14:58 Radeon DRM dom0 issues Michael D Labriola
2014-01-20 15:14 ` Konrad Rzeszutek Wilk
2014-01-20 15:26 ` Michael D Labriola
2014-01-20 15:38 ` Konrad Rzeszutek Wilk [this message]
2014-01-20 20:15 ` Michael D Labriola
2014-01-21 21:59 ` Konrad Rzeszutek Wilk
2014-01-23 16:54 ` Michael D Labriola
2014-01-24 14:49 ` Konrad Rzeszutek Wilk
2014-02-11 15:35 ` Michael D Labriola
2014-02-19 17:04 ` Konrad Rzeszutek Wilk
2014-02-19 19:33 ` Michael Labriola
2014-02-19 19:57 ` Konrad Rzeszutek Wilk
2014-02-19 20:08 ` Michael Labriola
2014-02-19 20:30 ` Konrad Rzeszutek Wilk
2014-02-19 21:02 ` Michael D Labriola
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=20140120153827.GA24989@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=konrad@darnok.org \
--cc=michael.d.labriola@gmail.com \
--cc=mlabriol@gdeb.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.