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: Fri, 06 Jun 2014 07:29:40 +0000	[thread overview]
Message-ID: <bug-51381-2300-YvIgJeJlyI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-51381-2300@https.bugzilla.kernel.org/>

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

--- Comment #22 from Teofilis Martisius <Teofilis.Martisius@gmail.com> ---
Ok,

I tried playing around with Linux 3.12, that's the last stable version before
that commit.

Booted with parameters:

[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.12-1-amd64
root=UUID=... ro quiet radeon.audio=0 modeset=1 radeon.dpm=1 radeon.no_wb=1
radeon.runpm=0

Executed:

echo OFF >/sys/kernel/debug/vgaswitcheroo/switch

dGPU got switched off, everything works fine. Got a message in dmesg:

[ 1454.396648] radeon: switched off

I don't want to spam attachments on this bug report, full dmesg output if
needed at:
http://menulis.org/kernel/dmesg_3.12_off1.log

I tried it with radeon.runpm=1 as well, same results, everything works fine.
Dmesg:
http://menulis.org/kernel/dmesg_3.12_off2.log

Let me know if you want these two dmesg logs attached here in bugzilla.

Let me know if you need me to try something else next.

Sincerely,
Teofilis Martisius

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2014-06-06  7:29 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
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 [this message]
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=bug-51381-2300-YvIgJeJlyI@https.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.