All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 16295] radeon conflict/interference with rt2800pci
Date: Sat, 3 Jul 2010 15:24:26 GMT	[thread overview]
Message-ID: <201007031524.o63FOQJC015417@demeter.kernel.org> (raw)
In-Reply-To: <bug-16295-2300@https.bugzilla.kernel.org/>

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


Alex Deucher <alexdeucher@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alexdeucher@gmail.com




--- Comment #7 from Alex Deucher <alexdeucher@gmail.com>  2010-07-03 15:24:23 ---
(In reply to comment #3)
> I'm getting confused. Now I get GPU lockups even without loading any WiFi
> driver :| It happens frequently with KDE4's effects enabled, not so often with
> effects disabled (but still).
> 
> It was really annoying to get lockup even every few seconds, so I decided to
> try removing "radeon_gpu_reset" from lockup handling. Now I get warnings in
> dmesg, but GPU continues to work (even without restarting).
> 
> However it's far from perfect solution.
> 
> Any idea how can I fix/debug that lockups?

I'd guess the GPU hasn't hung, but some fences haven't come up in a timely
enough manner that the driver attempts to reset the GPU thinking that it has
hung.  I'd guess an interrupt problem of some sort (either high latency in
dealing with interrupts or missed interrupts).  This would explain the GPU
reset as the fence code is interrupt driven.  Might be worth checking the CP
scratch regs in the hang check code to make sure it hasn't missed a fence in
which case a GPU reset isn't necessary.  Does disabling MSIs help?  try booting
with pci=nomsi

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
--

  parent reply	other threads:[~2010-07-03 15:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-25 19:37 [Bug 16295] New: radeon conflict/interference with rt2800pci bugzilla-daemon
2010-06-25 19:42 ` [Bug 16295] " bugzilla-daemon
2010-06-25 19:46 ` bugzilla-daemon
2010-07-02 20:51 ` bugzilla-daemon
2010-07-02 21:47 ` bugzilla-daemon
2010-07-02 22:37 ` bugzilla-daemon
2010-07-03 15:24 ` bugzilla-daemon [this message]
2012-08-09 14:12 ` 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=201007031524.o63FOQJC015417@demeter.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.