From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 27744] atombios stuck in loop - during suspend
Date: Tue, 4 May 2010 18:19:42 -0700 (PDT) [thread overview]
Message-ID: <20100505011943.0A51013004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-27744-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=27744
wessam <wbaghdadi@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Platform|x86-64 (AMD64) |x86 (IA32)
--- Comment #1 from wessam <wbaghdadi@gmail.com> 2010-05-04 18:19:42 PDT ---
I seem to be getting the same at startup (x86-64, Ububtu 10.04, Latest mainline
kernel - 2.6.34-020634rc6-generic; + xorg edgers ppa):
[ 14.911283] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
1sec aborting
[ 14.911289] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
FA2E (len 455, WS 0, PS 4) @ 0xFA6F
[ 15.951289] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
1sec aborting
[ 15.951295] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
FA2E (len 455, WS 0, PS 4) @ 0xFA6F
lspci -v
01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3650
Subsystem: Toshiba America Info Systems Device ff1e
Flags: bus master, fast devsel, latency 0, IRQ 31
Memory at c0000000 (32-bit, prefetchable) [size=256M]
I/O ports at 5000 [size=256]
Memory at d6400000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at d6420000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: radeon
Kernel modules: radeon
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2010-05-05 1:19 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 23:19 [Bug 27744] New: atombios stuck in loop - during suspend bugzilla-daemon
2010-05-05 1:19 ` bugzilla-daemon [this message]
2010-06-30 18:53 ` [Bug 27744] " bugzilla-daemon
2010-06-30 18:54 ` bugzilla-daemon
2010-06-30 18:54 ` bugzilla-daemon
2010-06-30 19:03 ` bugzilla-daemon
2010-06-30 19:55 ` bugzilla-daemon
2010-06-30 23:44 ` bugzilla-daemon
2010-07-22 18:32 ` bugzilla-daemon
2010-07-22 19:27 ` bugzilla-daemon
2010-07-22 23:29 ` bugzilla-daemon
2010-07-23 10:29 ` bugzilla-daemon
2010-07-30 17:23 ` bugzilla-daemon
2010-08-03 14:35 ` bugzilla-daemon
2010-08-03 14:37 ` bugzilla-daemon
2010-08-03 18:56 ` bugzilla-daemon
2010-08-08 13:51 ` bugzilla-daemon
2010-08-08 13:55 ` bugzilla-daemon
2010-08-09 16:39 ` bugzilla-daemon
2010-08-14 16:18 ` bugzilla-daemon
2010-08-14 18:48 ` bugzilla-daemon
2010-08-16 14:13 ` bugzilla-daemon
2010-08-16 15:44 ` bugzilla-daemon
2010-08-16 16:05 ` bugzilla-daemon
2010-08-16 16:33 ` bugzilla-daemon
2010-08-30 14:21 ` bugzilla-daemon
2010-08-30 14:21 ` bugzilla-daemon
2010-08-30 15:29 ` bugzilla-daemon
2010-08-30 15:30 ` bugzilla-daemon
2010-09-03 6:45 ` bugzilla-daemon
2010-09-03 6:46 ` bugzilla-daemon
2010-09-27 17:15 ` bugzilla-daemon
2010-10-02 10:44 ` bugzilla-daemon
2010-10-14 11:59 ` bugzilla-daemon
2010-10-21 10:28 ` bugzilla-daemon
2010-10-21 13:04 ` bugzilla-daemon
2010-10-24 17:23 ` bugzilla-daemon
2010-10-24 17:25 ` bugzilla-daemon
2010-10-28 7:54 ` bugzilla-daemon
2010-12-17 16:45 ` 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=20100505011943.0A51013004F@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.