All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29389] [r300g] [bisected] hard locks with polling enabled in 2.6.35
Date: Sun, 24 Oct 2010 14:40:13 -0700 (PDT)	[thread overview]
Message-ID: <20101024214013.AC9F413004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-29389-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=29389

--- Comment #6 from pj_beers@hotmail.com 2010-10-24 14:40:13 PDT ---
I reported the same bug (I think) over here:

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

Your latest patch disabling polling DACs works for my, I applied it to
2.6.36-rc7 and then ran Penumbra Overture without any problem. I'm using rv380,
not rv370 (according to dmesg). I've included dmesg output as an attachment.

Thanks very much for this patch!

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2010-10-24 21:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03 21:17 [Bug 29389] New: [r300g] [bisected] hard locks in openarena with kernel 2.6.35 bugzilla-daemon
2010-08-03 21:42 ` [Bug 29389] " bugzilla-daemon
2010-08-19 14:05 ` bugzilla-daemon
2010-08-26 16:09 ` bugzilla-daemon
2010-08-28  4:15 ` [Bug 29389] [r300g] [bisected] hard locks with polling enabled in 2.6.35 bugzilla-daemon
2010-08-28  4:21 ` bugzilla-daemon
2010-09-10 22:18 ` bugzilla-daemon
2010-10-21  0:27 ` bugzilla-daemon
2010-10-21  1:38 ` bugzilla-daemon
2010-10-24 21:40 ` bugzilla-daemon [this message]
2010-10-24 21:43 ` bugzilla-daemon
2010-10-25  8:51 ` bugzilla-daemon
2010-11-21 10:59 ` bugzilla-daemon
2010-11-21 12:17 ` bugzilla-daemon
2010-11-21 13:46 ` 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=20101024214013.AC9F413004E@annarchy.freedesktop.org \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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.