From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36642] Oops on vgaswitcheroo from intel IGD to radeon DIS.
Date: Sun, 25 Mar 2012 12:40:24 GMT [thread overview]
Message-ID: <201203251240.q2PCeOvm008922@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-36642-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=36642
Daniel Vetter <daniel@ffwll.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |daniel@ffwll.ch
Component|Video(DRI - Intel) |Video(DRI - non Intel)
AssignedTo|drivers_video-dri-intel@ker |drivers_video-dri@kernel-bu
|nel-bugs.osdl.org |gs.osdl.org
--- Comment #2 from Daniel Reurich <daniel@centurion.net.nz> 2011-06-04 13:15:16 ---
Sorry should have mentioned it happened on a Hewlett Packard Pavilion
DV7-6015tx laptop (17.3" Widescreen with after market ram upgrade to 8GB and
Intel 160GB MLC SSD.
Also, to clarify, the order of events was:
1) issued "echo DDIS > /sys/kernel/debug/vgaswitcheroo/switch" in ssh remote
terminal.
2) issued "/etc/init.d/gdm3 restart"
3) gdm shutdown and the lcd screen went blank and my ssh session froze.
4) attempted to establish another ssh session. This failed too.
5) attempted ctrl-alt-delete followed by pressing the power button.
I currently only have remote (ssh) access to the machine and rely on others to
be the eyes and ears.
I'm trying to get the ability to switch between the Integrated intel graphics
and the Discrete AMD/ATI radeon graphics devices.
Keen to help debug this further.
Daniel.
--- Comment #3 from Daniel Vetter <daniel@ffwll.ch> 2012-03-25 12:40:22 ---
I'm gonna blame radeon on this one ;-) Especially since the hang seems to only
happen when we start rendering on the radeon gpu (gdm3 starting), and at that
point drm/i915 shouldn't interfere with anything anymore at all ...
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next parent reply other threads:[~2012-03-25 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-36642-2300@https.bugzilla.kernel.org/>
2012-03-25 12:40 ` bugzilla-daemon [this message]
2012-03-25 13:35 ` [Bug 36642] Oops on vgaswitcheroo from intel IGD to radeon DIS bugzilla-daemon
2012-08-24 13:00 ` 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=201203251240.q2PCeOvm008922@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.