From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 40128] New: RV635 (Radeon HD 3600) failed to evaluate ATIF got AE_BAD_PARAMETER
Date: Tue, 16 Aug 2011 02:00:38 -0700 (PDT) [thread overview]
Message-ID: <bug-40128-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=40128
Summary: RV635 (Radeon HD 3600) failed to evaluate ATIF got
AE_BAD_PARAMETER
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: volodymyr@shcherbyna.com
Created an attachment (id=50258)
--> (https://bugs.freedesktop.org/attachment.cgi?id=50258)
dmesg output describing original problem
Hello,
I have HD 3600 and I am using Debian sid x86_64. I have noticed recently in my
dmesg output the following line: "failed to evaluate ATIF got AE_BAD_PARAMETER"
and I was suggested to file a bug here.
Please see attached full dmesg output of my machine.
Thank you,
V.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-08-16 9:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 9:00 bugzilla-daemon [this message]
2011-08-16 13:59 ` [Bug 40128] RV635 (Radeon HD 3600) failed to evaluate ATIF got AE_BAD_PARAMETER bugzilla-daemon
2011-08-16 21:02 ` bugzilla-daemon
2011-08-23 7:26 ` bugzilla-daemon
2011-08-23 8:05 ` bugzilla-daemon
2011-08-23 8:08 ` bugzilla-daemon
2011-08-29 21:43 ` [Bug 40128] GPU lockup (waiting for 0x0002F05C last fence id 0x0002F05A), oops in radeon_ring_write, and screen turns off bugzilla-daemon
2011-08-30 9:17 ` bugzilla-daemon
2019-11-19 8:20 ` 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=bug-40128-502@http.bugs.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.