From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108464] System fails to reboot after Ctrl-Alt-Del
Date: Sat, 27 Oct 2018 23:50:57 +0000 [thread overview]
Message-ID: <bug-108464-502-fmGQxkxMDf@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108464-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 981 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #10 from Duncan Roe <duncan_roe@optusnet.com.au> ---
(In reply to Alex Deucher from comment #1)
> Are you sure the bisect is correct? This commit just changes debugfs which
> shouldn't be triggered unless you actually write to the file in question.
> Please attach your xorg log (is using X) and dmesg output.
A fresh bisect in the stable tree has given a new pair of commits.
e1cb3e4801e6896ba93d63222b1052199d2a8c9b has the problem and
899e2aaddbfa0ff96fbaf31f0d9e91427e87dd88 does not have it. (In the stable tree,
30cdbfaa6aa469347db7fcda5949f1ccf7559ecf also has the problem, unlike in the
drm tree that I bisected previously).
A diff of the new commit pair shows 14 patched files. These are TODO, Makefile
and a mixture of .c and .h sources. I am unsure how to proceed with bisecting
these diffs: advice welcome.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1831 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 prev parent reply other threads:[~2018-10-27 23:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 21:59 [Bug 108464] System fails to reboot after Ctrl-Alt-Del bugzilla-daemon
2018-10-16 22:06 ` bugzilla-daemon
2018-10-16 22:28 ` bugzilla-daemon
2018-10-16 22:30 ` bugzilla-daemon
2018-10-16 22:41 ` bugzilla-daemon
2018-10-18 22:50 ` bugzilla-daemon
2018-10-24 22:38 ` bugzilla-daemon
2018-10-25 0:06 ` bugzilla-daemon
2018-10-25 7:40 ` bugzilla-daemon
2018-10-25 7:46 ` bugzilla-daemon
2018-10-27 23:50 ` bugzilla-daemon [this message]
2018-10-29 5:24 ` bugzilla-daemon
2018-11-03 9:28 ` bugzilla-daemon
2019-01-08 4:26 ` bugzilla-daemon
2019-01-08 4:43 ` bugzilla-daemon
2019-01-08 5:01 ` bugzilla-daemon
2019-01-08 14:01 ` bugzilla-daemon
2019-01-10 10:44 ` bugzilla-daemon
2019-01-10 11:04 ` bugzilla-daemon
2019-02-09 0:12 ` bugzilla-daemon
2019-02-09 0:24 ` bugzilla-daemon
2019-02-09 0:27 ` bugzilla-daemon
2019-02-09 1:13 ` bugzilla-daemon
2019-02-11 23:36 ` bugzilla-daemon
2019-02-11 23:42 ` bugzilla-daemon
2019-08-05 8:02 ` 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-108464-502-fmGQxkxMDf@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;
as well as URLs for NNTP newsgroup(s).