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 96470] [AMDGPU][CIK] PRIME doesn't work, X doesn't start at all (no screen found)
Date: Fri, 10 Jun 2016 05:06:54 +0000	[thread overview]
Message-ID: <bug-96470-502-EkCSrbCHAW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96470-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2496 bytes --]

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

--- Comment #2 from Shawn Starr <shawn.starr@rogers.com> ---
For reference, this doesn't work on radeon.ko anymore but due to a different
error from drm:

[   12.563839] radeon 0000:01:00.0: No connectors reported connected with modes
[ 12.564832] [drm] Cannot find any crtc or sizes - going 1024x768

And the ati DDX:

(EE) RADEON(G0): drmmode_do_crtc_dpms cannot get last vblank counter

And X crashing, the dGPU DDX would be I guess powered down if the intel iGPU
takes over.

[    19.327] (II) intel(0): EDID vendor "LGD", prod id 730
[    19.327] (II) intel(0): Printing DDC gathered Modelines:
[    19.327] (II) intel(0): Modeline "1920x1080"x0.0  140.00  1920 1968 2000
2096  1080 1083 1088 1113 -hsync -vsync (66.8 kHz eP)
[    19.429] (II) config/udev: removing GPU device
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card1 /dev/dri/card1
[    19.430] xf86: remove device 0
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card1
[    19.433] (II) UnloadModule: "radeon"
[    19.433] (II) UnloadSubModule: "glamoregl"
[    19.433] (II) Unloading glamoregl
[    19.433] (II) UnloadSubModule: "fb"
[    19.433] (II) Unloading fb
[    19.433] (EE) 
[    19.433] (EE) Backtrace:
[    19.444] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59fbd9]
[    19.468] (EE) 1: /lib64/libc.so.6 (__restore_rt+0x0) [0x7fdf3094276f]
[    19.468] (EE) 2: /usr/libexec/Xorg (RRTellChanged+0x165) [0x4f8c85]
[    19.468] (EE) 3: /usr/libexec/Xorg (xf86PlatformDeviceCheckBusID+0x2d6)
[0x49d016]
[    19.469] (EE) 4: /usr/libexec/Xorg (config_fini+0x7ef) [0x4994ef]
[    19.469] (EE) 5: /usr/libexec/Xorg (config_fini+0x13e0) [0x49ad20]
[    19.469] (EE) 6: /usr/libexec/Xorg (WakeupHandler+0x70) [0x43b860]
[    19.469] (EE) 7: /usr/libexec/Xorg (WaitForSomething+0x1e9) [0x598569]
[    19.469] (EE) 8: /usr/libexec/Xorg (SendErrorToClient+0x10e) [0x436b4e]
[    19.469] (EE) 9: /usr/libexec/Xorg (remove_fs_handlers+0x463) [0x43ad83]
[    19.469] (EE) 10: /lib64/libc.so.6 (__libc_start_main+0xf1)
[0x7fdf3092e731]
[    19.470] (EE) 11: /usr/libexec/Xorg (_start+0x29) [0x424bc9]
[    19.470] (EE) 12: ? (?+0x29) [0x29]
[    19.470] (EE) 
[    19.470] (EE) Segmentation fault at address 0x34
[    19.470] (EE) 
Fatal server error:
[    19.470] (EE) Caught signal 11 (Segmentation fault). Server aborting
[

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

[-- Attachment #1.2: Type: text/html, Size: 3379 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-06-10  5:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-10  1:14 [Bug 96470] [AMDGPU][CIK] PRIME doesn't work, X doesn't start at all (no screen found) bugzilla-daemon
2016-06-10  1:15 ` bugzilla-daemon
2016-06-10  1:15 ` bugzilla-daemon
2016-06-10  1:18 ` bugzilla-daemon
2016-06-10  1:18 ` bugzilla-daemon
2016-06-10  5:06 ` bugzilla-daemon [this message]
2016-06-10  5:12 ` bugzilla-daemon
2016-06-10  6:10 ` bugzilla-daemon
2016-06-10  8:13 ` bugzilla-daemon
2016-08-31  3:29 ` bugzilla-daemon
2016-08-31  3:59 ` 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-96470-502-EkCSrbCHAW@http.bugs.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