From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 59982] New: Radeon: evergreen Atombios in loop during initialization on ppc64
Date: Mon, 28 Jan 2013 18:37:52 +0000 [thread overview]
Message-ID: <bug-59982-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1536 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=59982
Priority: medium
Bug ID: 59982
Assignee: dri-devel@lists.freedesktop.org
Summary: Radeon: evergreen Atombios in loop during
initialization on ppc64
Severity: normal
Classification: Unclassified
OS: All
Reporter: lucaskt@linux.vnet.ibm.com
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Created attachment 73788
--> https://bugs.freedesktop.org/attachment.cgi?id=73788&action=edit
Log for module insertion errors on mainline
During the initialization of an evergreen adapter on ppc64 there are a lot of
atombios problems reported, though none seems fatal.
This is in sequence to bug #59672. Though this is now being run on the
3.8.0-rc5 kernel. The problem is basically a bunch of messages like:
[ 854.915511] [drm:drm_vblank_get], enabling vblank on crtc 0, ret: 0
[ 854.915520] [drm:drm_calc_vbltimestamp_from_scanoutpos], crtc 0: Noop due to
uninitialized mode.
[ 854.915526] [drm:drm_update_vblank_count], enabling vblank interrupts on
crtc 0, missed -1
[ 859.924406] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
5secs aborting
[ 859.924416] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
C898 (len 62, WS 0, PS 0) @ 0xC8B4
A full dump is included as an attachment.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3193 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-01-28 18:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 18:37 bugzilla-daemon [this message]
2013-01-28 18:38 ` [Bug 59982] Radeon: evergreen Atombios in loop during initialization on ppc64 bugzilla-daemon
2013-01-29 3:45 ` bugzilla-daemon
2013-01-29 3:46 ` bugzilla-daemon
2013-01-29 12:42 ` bugzilla-daemon
2013-01-29 12:50 ` bugzilla-daemon
2013-01-30 19:49 ` bugzilla-daemon
2013-01-31 10:57 ` bugzilla-daemon
2013-01-31 15:12 ` bugzilla-daemon
2013-02-06 17:07 ` bugzilla-daemon
2013-02-06 17:08 ` bugzilla-daemon
2013-02-08 17:17 ` bugzilla-daemon
2013-02-08 17:20 ` bugzilla-daemon
2013-02-09 14:40 ` bugzilla-daemon
2013-02-13 13:38 ` bugzilla-daemon
2013-02-13 14:08 ` bugzilla-daemon
2013-02-18 16:22 ` bugzilla-daemon
2013-02-18 16:29 ` bugzilla-daemon
2013-02-20 14:47 ` bugzilla-daemon
2013-02-20 15:33 ` bugzilla-daemon
2013-02-20 15:34 ` bugzilla-daemon
2013-02-20 16:33 ` bugzilla-daemon
2013-02-20 18:54 ` bugzilla-daemon
2013-02-20 22:03 ` bugzilla-daemon
2013-02-22 12:52 ` bugzilla-daemon
2013-02-22 15:04 ` bugzilla-daemon
2013-02-27 14:24 ` bugzilla-daemon
2013-02-27 14:26 ` bugzilla-daemon
2013-02-27 15:08 ` bugzilla-daemon
2013-02-27 15:47 ` bugzilla-daemon
2013-02-27 16:29 ` bugzilla-daemon
2013-02-27 17:21 ` bugzilla-daemon
2013-02-27 17:44 ` bugzilla-daemon
2013-02-28 17:34 ` 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-59982-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox