All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 34772] [radeon] [R300] GPU lockups with when KMS is enabled
Date: Sat, 21 May 2011 15:34:41 GMT	[thread overview]
Message-ID: <201105211534.p4LFYfBa016952@demeter2.kernel.org> (raw)
In-Reply-To: <bug-34772-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=34772





--- Comment #17 from Rogério Brito <rbrito@ime.usp.br>  2011-05-21 15:34:37 ---
Hi, Michel.

Thank you very much for the attention.

(In reply to comment #16)
> When the kernel radeon driver fails to initialize acceleration, there's no
> point in trying any functionality that needs acceleration, such as XVideo.

OK.

> I don't think there's any point doing any more tests with 2.6.39-rc7, as it's
> obviously suffering from additional issues which only occurred intermittently
> during the 2.6.39 cycle.

Right.

> Well, I'm afraid less quantity but more quality would be better... It's
> becoming rather difficult and time-consuming to find the relevant pieces of
> information in this mass.

Indeed, it is getting out of hand pretty quickly. Do you want me to give you
some SSH access to this notebook? Or, if that's not feasible/useful, what would
you like me to test as the next step, so that I avoid flooding you with so much
data?

> Has either of you tried agpmode=1 dynclks=1? Does that increase stability at
> all?

I will try those. But with which kernel? I have been avoiding compiling a
kernel nowadays, since they take ages on this notebook, but I can set up a
cross-compilation environment, if necessary.

BTW, would you mind sharing your .config?

> I thought there was some kind of multimedia adapter for the external output.

The only external adapter is one to a VGA port. No traces of S-video here.

> But really, we need to focus on one problem per bug report as much as possible,
> or things are getting out of hand.

OK, I can file a separate bug for this S-Video issue, then.



Thank you so much for your patience,

Rogério Brito.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

  parent reply	other threads:[~2011-05-21 15:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 23:26 [Bug 34772] New: [radeon] [R300] GPU lockups with when KMS is enabled bugzilla-daemon
2011-05-19 20:34 ` [Bug 34772] " bugzilla-daemon
2011-05-19 20:36 ` bugzilla-daemon
2011-05-19 20:37 ` bugzilla-daemon
2011-05-19 20:38 ` bugzilla-daemon
2011-05-19 20:38 ` bugzilla-daemon
2011-05-20 12:12 ` bugzilla-daemon
2011-05-20 14:31 ` bugzilla-daemon
2011-05-20 20:58 ` bugzilla-daemon
2011-05-21  9:16 ` bugzilla-daemon
2011-05-21  9:23 ` bugzilla-daemon
2011-05-21  9:34 ` bugzilla-daemon
2011-05-21  9:42 ` bugzilla-daemon
2011-05-21  9:47 ` bugzilla-daemon
2011-05-21  9:50 ` bugzilla-daemon
2011-05-21  9:56 ` bugzilla-daemon
2011-05-21 14:54 ` bugzilla-daemon
2011-05-21 15:34 ` bugzilla-daemon [this message]
2011-05-21 15:38 ` bugzilla-daemon
2011-05-21 15:42 ` bugzilla-daemon
2011-05-21 16:47 ` bugzilla-daemon
2011-05-21 16:59 ` bugzilla-daemon
2012-08-23 14:05 ` bugzilla-daemon
2012-10-28 18:51 ` bugzilla-daemon
2014-06-25  2:02 ` bugzilla-daemon
2014-06-28 10:45 ` bugzilla-daemon

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=201105211534.p4LFYfBa016952@demeter2.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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.