From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101832] [regression][bisect] sddm fails to start after f50aa21456d82c8cb6fbaa565835f1acc1720a5d
Date: Tue, 18 Jul 2017 23:06:29 +0000 [thread overview]
Message-ID: <bug-101832-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2967 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101832
Bug ID: 101832
Summary: [regression][bisect] sddm fails to start after
f50aa21456d82c8cb6fbaa565835f1acc1720a5d
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: blocker
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: lordheavym@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 132751
--> https://bugs.freedesktop.org/attachment.cgi?id=132751&action=edit
xorg log file with the segfault
* llvm-svn 308274
* AMD Radeon RX 470 Graphics (AMD POLARIS10 / DRM 3.15.0 / 4.12.2-1-ARCH, LLVM
5.0.0)
Bisecting gives:
f50aa21456d82c8cb6fbaa565835f1acc1720a5d is the first bad commit
commit f50aa21456d82c8cb6fbaa565835f1acc1720a5d
Author: Tim Rowley <timothy.o.rowley@intel.com>
Date: Thu Jun 29 14:37:07 2017 -0500
swr: build driver proper separate from rasterizer
bisect log:
git bisect start
# good: [6c7b7aa3d8323a7cde5ab2b84fabc16913adeab4] a5xx: fix condition for
updating *_FS_OUTPUT_CNTL
git bisect good 6c7b7aa3d8323a7cde5ab2b84fabc16913adeab4
# bad: [28ccf8587e1e1c0e9a7b08296807c343f33dc9de] i965/gen4: Set tile offsets
to zero after depth rebase
git bisect bad 28ccf8587e1e1c0e9a7b08296807c343f33dc9de
# bad: [2b895475f600b142e9ccbfb3b33009fe68b21162] util: Remove u_math from
u_vector
git bisect bad 2b895475f600b142e9ccbfb3b33009fe68b21162
# bad: [aadd37298c704982036f64e58903c80cd7dac93b] i965/miptree: Add a return
for updating of winsys
git bisect bad aadd37298c704982036f64e58903c80cd7dac93b
# bad: [4d8191fd000071328b97bde5fc31ab1c39238d27] egl: check for extensions'
presence during attr parsing
git bisect bad 4d8191fd000071328b97bde5fc31ab1c39238d27
# good: [618be8cc1ad1760103930b69ffbf528d7b861ab3] i965: Resolve framebuffers
before signaling the fence
git bisect good 618be8cc1ad1760103930b69ffbf528d7b861ab3
# bad: [314879f7fec07cedb5263681173a22d522a8ac9a] i965: Fix asynchronous
mappings on !LLC platforms.
git bisect bad 314879f7fec07cedb5263681173a22d522a8ac9a
# good: [27c5568de3674ec95f02816a06b13180bad0838b] swr/rast: make SWR_VISIBLE
attribute work for windows
git bisect good 27c5568de3674ec95f02816a06b13180bad0838b
# bad: [f50aa21456d82c8cb6fbaa565835f1acc1720a5d] swr: build driver proper
separate from rasterizer
git bisect bad f50aa21456d82c8cb6fbaa565835f1acc1720a5d
# good: [50cd222116b40e4df2462cb25a92960d557c9144] swr: switch to using
SwrGetInterface api table
git bisect good 50cd222116b40e4df2462cb25a92960d557c9144
# first bad commit: [f50aa21456d82c8cb6fbaa565835f1acc1720a5d] swr: build
driver proper separate from rasterizer
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4574 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
next reply other threads:[~2017-07-18 23:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 23:06 bugzilla-daemon [this message]
2017-07-19 10:47 ` [Bug 101832] [regression][bisect] sddm fails to start after f50aa21456d82c8cb6fbaa565835f1acc1720a5d bugzilla-daemon
2017-07-19 13:22 ` bugzilla-daemon
2017-07-19 14:06 ` bugzilla-daemon
2017-07-19 14:14 ` bugzilla-daemon
2017-07-21 13:00 ` bugzilla-daemon
2017-07-24 15:30 ` bugzilla-daemon
2017-07-24 15:54 ` bugzilla-daemon
2017-08-16 10: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-101832-502@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