From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 16295] radeon conflict/interference with rt2800pci
Date: Fri, 2 Jul 2010 21:47:58 GMT [thread overview]
Message-ID: <201007022147.o62LlwJ5009581@demeter.kernel.org> (raw)
In-Reply-To: <bug-16295-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=16295
--- Comment #5 from Rafał Miłecki <zajec5@gmail.com> 2010-07-02 21:47:56 ---
Created an attachment (id=27002)
--> (https://bugzilla.kernel.org/attachment.cgi?id=27002)
dmesg with rt2x00pci_regbusy_read: Error - Indirect register access failed
Now for difference I get "Indirect register access failed" error immediately
after loading rt2800pci second time. GPU doesn't even have time to lockup...
--
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
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next prev parent reply other threads:[~2010-07-02 21:47 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 [this message]
2010-07-02 22:37 ` bugzilla-daemon
2010-07-03 15:24 ` bugzilla-daemon
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=201007022147.o62LlwJ5009581@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox