All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 198883] amdgpu: carrizo: Screen stalls after starting X
Date: Fri, 09 Mar 2018 15:46:34 +0000	[thread overview]
Message-ID: <bug-198883-2300-aSv1z60gqE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198883-2300@https.bugzilla.kernel.org/>

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

--- Comment #42 from Ricardo Ribalda (ricardo.ribalda@gmail.com) ---
With current LLVM7 master X does not start at all. I get the following output:

root@qt5122:~# X

X.Org X Server 1.19.3
Release Date: 2017-03-15
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.14.0-3-amd64 x86_64 
Current Operating System: Linux qt5122 4.16.0-rc4-qtec-standard #1 SMP Fri Mar
9 15:13:05 CET 2018 x86_64
Kernel command line: BOOT_IMAGE=/boot/bzImage rw root=PARTUUID=c839955a-02
rootwait qtec_mem.size=64 quiet
Build Date: 09 March 2018  02:29:53PM

Current version of pixman: 0.34.0
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar  9 15:47:03 2018
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) [KMS] Kernel modesetting enabled.
LLVM ERROR: Cannot select: 0x7f74b40a59e0: v4i32,ch =
load<LD16[%22(addrspace=2)](dereferenceable)(invariant)> 0x7f74b40251c8,
0x7f74b40a5978, undef:i32
  0x7f74b40a5978: i32 = add 0x7f74b409f378, Constant:i32<16>
    0x7f74b409f378: i32,ch = CopyFromReg 0x7f74b40251c8, Register:i32 %4
      0x7f74b409f310: i32 = Register %4
    0x7f74b40a5910: i32 = Constant<16>
  0x7f74b409fc68: i32 = undef
In function: main
LLVM ERROR: Cannot select: 0x7f74a00b0570: v4i32,ch =
load<LD16[%22(addrspace=2)](dereferenceable)(invariant)> 0x7f74a002eab8,
0x7f74a00b0508, undef:i32
  0x7f74a00b0508: i32 = add 0x7f74a00a9f08, Constant:i32<16>
    0x7f74a00a9f08: i32,ch = CopyFromReg 0x7f74a002eab8, Register:i32 %4
      0x7f74a00a9ea0: i32 = Register %4
    0x7f74a00b04a0: i32 = Constant<16>
  0x7f74a00aa7f8: i32 = undef
In function: main
root@qt5122:~#

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-03-09 15:46 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22 10:46 [Bug 198883] New: amdgpu: carrizo: Screen stalls after starting X bugzilla-daemon
2018-02-22 10:47 ` [Bug 198883] " bugzilla-daemon
2018-02-22 10:47 ` bugzilla-daemon
2018-02-22 10:47 ` bugzilla-daemon
2018-02-23 13:02 ` bugzilla-daemon
2018-02-23 15:01 ` bugzilla-daemon
2018-02-23 15:02 ` bugzilla-daemon
2018-02-23 15:02 ` bugzilla-daemon
2018-02-23 15:14 ` bugzilla-daemon
2018-02-23 15:19 ` bugzilla-daemon
2018-02-23 15:23 ` bugzilla-daemon
2018-02-23 15:29 ` bugzilla-daemon
2018-02-23 15:29 ` bugzilla-daemon
2018-02-23 15:31 ` bugzilla-daemon
2018-02-23 15:33 ` bugzilla-daemon
2018-02-23 15:34 ` bugzilla-daemon
2018-02-23 15:42 ` bugzilla-daemon
2018-02-23 15:45 ` bugzilla-daemon
2018-02-23 20:20 ` bugzilla-daemon
2018-02-23 21:44 ` bugzilla-daemon
2018-02-24  6:41 ` bugzilla-daemon
2018-02-24 14:04 ` bugzilla-daemon
2018-02-26 16:11 ` bugzilla-daemon
2018-02-27 13:57 ` bugzilla-daemon
2018-02-27 13:58 ` bugzilla-daemon
2018-03-05 13:26 ` bugzilla-daemon
2018-03-05 14:01 ` bugzilla-daemon
2018-03-05 14:02 ` bugzilla-daemon
2018-03-05 14:03 ` bugzilla-daemon
2018-03-05 17:27 ` bugzilla-daemon
2018-03-05 21:22 ` bugzilla-daemon
2018-03-06  8:08 ` bugzilla-daemon
2018-03-06  8:09 ` bugzilla-daemon
2018-03-06  8:23 ` bugzilla-daemon
2018-03-06  8:24 ` bugzilla-daemon
2018-03-06 12:52 ` bugzilla-daemon
2018-03-06 13:38 ` bugzilla-daemon
2018-03-06 13:39 ` bugzilla-daemon
2018-03-06 14:07 ` bugzilla-daemon
2018-03-06 16:39 ` bugzilla-daemon
2018-03-06 16:53 ` bugzilla-daemon
2018-03-06 17:54 ` bugzilla-daemon
2018-03-09 15:46 ` bugzilla-daemon [this message]
2018-03-09 16:08 ` bugzilla-daemon
2018-03-09 18:31 ` bugzilla-daemon
2018-03-09 18:38 ` bugzilla-daemon
2018-03-12  8:12 ` bugzilla-daemon
2018-03-12 11:00 ` bugzilla-daemon
2018-03-12 11:55 ` bugzilla-daemon
2018-03-12 12:04 ` bugzilla-daemon
2018-03-12 12:04 ` bugzilla-daemon
2018-03-12 14:12 ` bugzilla-daemon
2018-03-12 14:32 ` bugzilla-daemon
2018-03-12 14:33 ` bugzilla-daemon
2018-03-12 14:40 ` bugzilla-daemon
2018-03-12 14:41 ` bugzilla-daemon
2018-03-12 14:42 ` bugzilla-daemon
2018-03-14  8:14 ` bugzilla-daemon
2018-03-15 17:59 ` bugzilla-daemon
2018-03-16 11:11 ` bugzilla-daemon
2018-03-16 14:37 ` bugzilla-daemon
2018-03-20  8:48 ` bugzilla-daemon
2018-03-20 11:58 ` bugzilla-daemon
2018-03-20 15:10 ` bugzilla-daemon
2018-03-20 16:27 ` bugzilla-daemon
2018-03-21  8:29 ` bugzilla-daemon
2018-03-21 12:41 ` bugzilla-daemon
2018-03-21 13:45 ` bugzilla-daemon
2018-03-21 14:23 ` bugzilla-daemon
2018-03-21 14:33 ` bugzilla-daemon
2018-03-21 14:33 ` bugzilla-daemon
2018-03-21 14:34 ` bugzilla-daemon
2018-03-22 12:18 ` bugzilla-daemon
2018-03-22 13:27 ` bugzilla-daemon
2018-03-22 13:47 ` bugzilla-daemon
2018-03-22 13:48 ` bugzilla-daemon
2018-03-22 14:02 ` bugzilla-daemon
2018-03-22 14:43 ` bugzilla-daemon
2018-04-08 22:30 ` bugzilla-daemon
2018-04-09  6:39 ` bugzilla-daemon
2018-04-09 13:18 ` bugzilla-daemon
2018-04-10 14:46 ` bugzilla-daemon
2018-04-10 14:49 ` bugzilla-daemon
2018-04-16 14:04 ` bugzilla-daemon
2018-04-16 14:56 ` bugzilla-daemon
2018-04-16 15:13 ` bugzilla-daemon
2018-04-20 12:19 ` bugzilla-daemon
2018-04-20 12:22 ` bugzilla-daemon
2018-04-20 12:23 ` 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-198883-2300-aSv1z60gqE@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.