From: Lee Revell <rlrevell@joe-job.com>
To: Mark Knecht <markknecht@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Gerhard Mack <gmack@innerfire.net>,
LKML <linux-kernel@vger.kernel.org>,
Xavier Bestel <xavier.bestel@free.fr>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Hugo Mills <hugo-lkml@carfax.org.uk>, Nix <nix@esperi.org.uk>,
Anshuman Gholap <anshu.pg@gmail.com>,
Diego Calleja <diegocg@gmail.com>,
Toon van der Pas <toon@hout.vanvergehaald.nl>,
arjan@infradead.org
Subject: Re: 3D video card recommendations
Date: Sat, 12 Nov 2005 04:11:40 -0500 [thread overview]
Message-ID: <1131786700.13373.37.camel@mindpipe> (raw)
In-Reply-To: <5bdc1c8b0511071123h4a1d0da7rcae0548c2c55afb3@mail.gmail.com>
On Mon, 2005-11-07 at 11:23 -0800, Mark Knecht wrote:
> On 11/7/05, Lee Revell <rlrevell@joe-job.com> wrote:
> >
> > Um, didn't you say you were still getting audio underruns correlated
> > with display activity? I still think it's a bug in the Xorg radeon
> > driver.
> >
> > Lee
>
> Hi Lee,
> It very well could be a video issue causing my xruns. That's been
> the biggest, but not olny, factor, but I don't know any more. I've
> gone down so many paths that haven't yielded results.
>
> I've tried the NoAccel and RenderAccel experiments you suggested.
> You also mentioned not loading DRI which I guess isn't possible anyway
> with a PCI-Express card. Anyway, I don't have it loaded.
>
> While I do get xruns, they are happening lately only a couple of
> times a day, and usually very late in the day after the machine has
> been running for 12+ hours. If I pull Jack back to 256/2 then I don't
> think I get them at all so I'm living with it for now and hoping for a
> solution one of these days. Low latency really only matters to me when
> recording which is <5% of the time.
After looking at the Radeon driver I'm increasingly convinced that it's
causing your problems.
Please try disabling Xscreensaver and see if the xruns go away - looking
at radeonfb it seems like the xruns could be triggered by video mode
switching, there are lots of places where it loops waiting for the
hardware to be ready. If that eliminates them I have a patch you can
try.
Lee
next prev parent reply other threads:[~2005-11-12 9:13 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 13:56 3D video card recommendations Steven Rostedt
2005-11-04 15:10 ` Mark Knecht
2005-11-04 15:14 ` Paweł Sikora
2005-11-04 15:22 ` Steven Rostedt
[not found] ` <ec92bc30511040730g2ad412ddsb3ac63f701de6c97@mail.gmail.com>
2005-11-04 15:39 ` Anshuman Gholap
2005-11-06 23:46 ` Nix
2005-11-07 7:42 ` Arjan van de Ven
2005-11-07 12:42 ` Steven Rostedt
2005-11-07 12:55 ` Hugo Mills
2005-11-07 14:22 ` Paweł Sikora
2005-11-07 15:07 ` Paweł Sikora
2005-11-07 14:51 ` Ville Syrjälä
2005-11-07 15:50 ` Jerome Glisse
2005-11-07 16:24 ` Gerhard Mack
2005-11-07 16:35 ` Ian Romanick
2005-11-07 16:41 ` Ville Syrjälä
2005-11-07 14:24 ` Alan Cox
2005-11-07 13:59 ` Xavier Bestel
2005-11-07 16:17 ` Gerhard Mack
2005-11-07 15:20 ` Toon van der Pas
2005-11-07 15:31 ` Arjan van de Ven
2005-11-07 17:35 ` Steven Rostedt
2005-11-08 22:08 ` Matthias Andree
2005-11-08 22:18 ` John Stoffel
2005-11-08 22:37 ` Tue, 8 Nov 2005 23:37:43 +0100
2005-11-09 1:34 ` Alan Cox
2005-11-07 17:00 ` Diego Calleja
2005-11-07 17:30 ` Steven Rostedt
2005-11-07 17:44 ` Gerhard Mack
2005-11-07 17:53 ` Steven Rostedt
2005-11-07 17:56 ` Gerhard Mack
2005-11-07 18:01 ` Mark Knecht
2005-11-07 18:15 ` Steven Rostedt
2005-11-07 18:31 ` Mark Knecht
2005-11-07 19:08 ` Gerhard Mack
2005-11-07 19:09 ` Mark Knecht
2005-11-07 19:05 ` Lee Revell
2005-11-07 19:23 ` Mark Knecht
2005-11-07 19:47 ` Steven Rostedt
2005-11-12 9:11 ` Lee Revell [this message]
2005-11-07 18:19 ` Joel Jaeggli
2005-11-08 18:59 ` Stefan Seyfried
2005-11-08 19:06 ` Lennart Sorensen
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=1131786700.13373.37.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anshu.pg@gmail.com \
--cc=arjan@infradead.org \
--cc=diegocg@gmail.com \
--cc=gmack@innerfire.net \
--cc=hugo-lkml@carfax.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@gmail.com \
--cc=nix@esperi.org.uk \
--cc=rostedt@goodmis.org \
--cc=toon@hout.vanvergehaald.nl \
--cc=xavier.bestel@free.fr \
/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