dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 27744] atombios stuck in loop - during suspend
Date: Thu, 22 Jul 2010 11:32:54 -0700 (PDT)	[thread overview]
Message-ID: <20100722183255.06B1B1300FF@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-27744-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=27744

--- Comment #8 from willjcroz <willjcroz@yahoo.co.uk> 2010-07-22 11:32:54 PDT ---
I get the same errors as listed above during resume from suspen (RAM) on Ubuntu
PPA kernel 2.6.35-rc5 (x86_64 Ubuntu 10.04 with ATI X1400 mobile chip in
Thinkpad T60). On my system the screen displays the errors and hangs on the
VT/framebuffer and requires a hard reset.

Additionally they are always proceeded by pciehp messages complaining that a
device already exists (maybe related here?). This is what I see:

[   70.630060] pciehp 0000:00:1c.0:pcie04: Device 0000:02:00.0 already exists
at 0000:02:00, cannot hot add
[   70.630063] pciehp 0000:00:1c.0:pcie04: Cannot add device at 0000:02:00
[   71.336223] usb 3-1: sierra_reset_resume
[   72.160012] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
1sec aborting
[   72.160016] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
EB96 (len 86, WS 4, PS 0) @ 0xEBC9

(there may be a typo or two, the errors above were written down by hand)

I have been having the pciehp errors (and subsequent hang) during resume since
I installed 2.6.34 stable, the atombios errors appeared in the 2.6.35 RCs I
think.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2010-07-22 18:32 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 ` [Bug 27744] " bugzilla-daemon
2010-06-30 18:53 ` 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 [this message]
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=20100722183255.06B1B1300FF@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox