All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 51381] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo
Date: Thu, 13 Jun 2013 17:10:14 +0000 (UTC)	[thread overview]
Message-ID: <20130613171014.32C4111FBC3@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-51381-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=51381


Christoph Haag <haagch.christoph@googlemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |haagch.christoph@googlemail
                   |                            |.com




--- Comment #6 from Christoph Haag <haagch.christoph@googlemail.com>  2013-06-13 17:10:13 ---
intel + radeon + vgaswitcheroo seems to have been problematic for quite some
time:
https://bugzilla.kernel.org/show_bug.cgi?id=23592

I'm using 3.10rc5.

While I have no problems with suspending or quitting X (didn't have problems
with some earlier kernels either), I have had yet another problem for some time
now. If I

start X with the radeon card enabled
then disable the radeon card with vgaswitcheroo
then switch to a tty
then switch back to X

then X hangs and I get many messages like
[  236.688466] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
5secs aborting
[  236.688470] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
D46E (len 62, WS 0, PS 0) @ 0xD48A

I assume the problem is still the same.

The most pressing issue is that X should not get stuck, no matter what. It's
much better to reset the driver somehow, even if you lose 3d acceleration or
so. As it is now, X eats all keyboard input and you have to use sysrq keys or
reboot over ssh which is not really ideal.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2013-06-13 17:10 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07 11:00 [Bug 51381] New: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo bugzilla-daemon
2012-12-07 14:27 ` [Bug 51381] " bugzilla-daemon
2012-12-07 16:18 ` bugzilla-daemon
2012-12-07 16:22 ` bugzilla-daemon
2012-12-07 16:22 ` bugzilla-daemon
2012-12-07 17:34 ` bugzilla-daemon
2012-12-09 13:55 ` bugzilla-daemon
2013-06-13 17:10 ` bugzilla-daemon [this message]
2013-06-13 17:11 ` bugzilla-daemon
2014-05-04 17:28 ` bugzilla-daemon
2014-05-04 17:32 ` bugzilla-daemon
2014-05-04 17:36 ` bugzilla-daemon
2014-05-05 13:33 ` bugzilla-daemon
2014-05-05 17:44 ` bugzilla-daemon
2014-06-04 20:43 ` bugzilla-daemon
2014-06-04 20:59 ` bugzilla-daemon
2014-06-04 21:51 ` bugzilla-daemon
2014-06-04 21:53 ` bugzilla-daemon
2014-06-05  6:18 ` bugzilla-daemon
2014-06-05 13:21 ` bugzilla-daemon
2014-06-05 22:38 ` bugzilla-daemon
2014-06-05 22:40 ` bugzilla-daemon
2014-06-05 22:43 ` bugzilla-daemon
2014-06-06  7:08 ` bugzilla-daemon
2014-06-06  7:29 ` bugzilla-daemon
2014-06-06 14:17 ` bugzilla-daemon
2014-06-06 21:04 ` bugzilla-daemon
2014-06-06 21:05 ` bugzilla-daemon
2014-06-06 21:13 ` bugzilla-daemon
2014-06-06 21:14 ` bugzilla-daemon
2014-06-09 18:18 ` bugzilla-daemon
2014-06-09 18:19 ` bugzilla-daemon
2014-06-09 18:20 ` bugzilla-daemon
2014-06-09 18:22 ` bugzilla-daemon
2014-06-09 18:27 ` bugzilla-daemon
2014-06-10  6:28 ` bugzilla-daemon
2014-06-10  6:29 ` bugzilla-daemon
2014-06-28 13:12 ` bugzilla-daemon
2014-07-18 16:00 ` bugzilla-daemon
2014-07-19  9:52 ` bugzilla-daemon
2014-09-22  6:00 ` bugzilla-daemon
2014-09-22 21:39 ` bugzilla-daemon
2016-03-12 18:58 ` bugzilla-daemon
2016-04-26 14:35 ` bugzilla-daemon
2016-09-02  3:25 ` bugzilla-daemon
2016-09-02 13:35 ` bugzilla-daemon
2016-09-02 19:59 ` bugzilla-daemon
2016-09-05 21:03 ` bugzilla-daemon
2016-09-08 23:19 ` bugzilla-daemon
2016-09-08 23:21 ` bugzilla-daemon
2016-09-08 23:30 ` bugzilla-daemon
2016-10-11  0:16 ` bugzilla-daemon
2016-10-28 21:24 ` bugzilla-daemon
2016-12-11 16:31 ` bugzilla-daemon
2018-04-07 15:10 ` bugzilla-daemon
2021-02-28  8:07 ` bugzilla-daemon
2021-05-07  9:34 ` bugzilla-daemon
2021-05-07 10:32 ` bugzilla-daemon
2021-05-08  7:31 ` bugzilla-daemon
2021-05-08 17:49 ` bugzilla-daemon
2021-05-08 19:27 ` bugzilla-daemon
2021-05-09  4:16 ` bugzilla-daemon
2021-05-11 10:03 ` 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=20130613171014.32C4111FBC3@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.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.