From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100673] Tonga agd5f drm-next-4.12-wip xorg segfault on startx
Date: Thu, 13 Apr 2017 11:43:05 +0000 [thread overview]
Message-ID: <bug-100673-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1068 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100673
Bug ID: 100673
Summary: Tonga agd5f drm-next-4.12-wip xorg segfault on startx
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: adf.lists@gmail.com
Created attachment 130829
--> https://bugs.freedesktop.org/attachment.cgi?id=130829&action=edit
xorg log with segfault
With current agd5f drm-next-4.12-wip I get a segfault on startx (xserver
1.19.3, git ddx,mesa,llvm. Log attached.
On the previous incarnation of the same kernel I can startx, but there are a
lot of warnings in dmesg every time the screen is turned on - ie. startx or
coming out of dpms. dmesg attached.
Don't know when I'll get time to bisect, so just getting these reported now.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2505 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-04-13 11:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 11:43 bugzilla-daemon [this message]
2017-04-13 11:44 ` [Bug 100673] Tonga agd5f drm-next-4.12-wip xorg segfault on startx bugzilla-daemon
2017-04-13 13:49 ` bugzilla-daemon
2017-04-13 19:56 ` bugzilla-daemon
2017-04-13 20:33 ` bugzilla-daemon
2017-04-13 22:04 ` bugzilla-daemon
2017-04-13 22:11 ` bugzilla-daemon
2017-04-21 14:54 ` 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-100673-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 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.