From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108464] System fails to reboot after Ctrl-Alt-Del
Date: Thu, 10 Jan 2019 11:04:12 +0000 [thread overview]
Message-ID: <bug-108464-502-POsUtR9Ci3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108464-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 965 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #18 from Duncan Roe <duncan_roe@optusnet.com.au> ---
Mixed results on applying this patch.
IN BRIEF: If you could eliminate this second Oops then we can see what works
and what doesn't.
In the meantime with the patch applied to v4.20 in the stable repository:
reboot *sometimes* works. Ctl-Alt-Del w/out logging in seems not to. Log in as
root and issue reboot cmd: no. Well it did work for me a couple of times but I
can't seem to be able to do it again.
Another thing: I boot to command level. If I let the VC time out (backlight
goes off) then I can never wake it again no matter what keys I press. Caps Lock
light goes on and off, so keyboard is still active.
Hopefully this all gets better once there is no Oops.
Attachment 143055 pinpoints the immediate NULL pointer. Again this is a new
aux_engine.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2009 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:[~2019-01-10 11:04 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
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 [this message]
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-POsUtR9Ci3@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).