From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108037] Turning monitors off and on again makes the kernel panic and system freeze
Date: Mon, 24 Sep 2018 16:46:31 +0000 [thread overview]
Message-ID: <bug-108037-502-ISMw9nvDEP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108037-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1310 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108037
--- Comment #3 from Öyvind Saether <oyvinds@everdot.org> ---
(In reply to Michel Dänzer from comment #1)
> Can you bisect?
> P.S. FYI, this is what's called an oops, not a panic.
oops, then. yes I now know how to bisect. I can.
(In reply to Alex Deucher from comment #2)
> When you say turn them off/on, do you mean via software (e.g., dpms) or via
> the switch on the monitor?
I used the actual power button on the monitors that have them and the stupid
joystick thing on the third monitor (works like a button) when this first
happens but I just found that it doesn't matter, triggered it on 4.18.9 with
dpms too.
On 4.18.9:
> set xscreensaver to immediately turn monitors off with dpms
> lock screen
> wait for monitors go into suspend
> press button on keyboard
> monitors don't come back on, system freeze
will attach same-problem-4.18.9.txt with that one. 4.18.5 is fine. I notice
there was a lot of amdgpu changes between 4.18.7 and 4.18.8 in the log. I have
used 4.19 git kernels for some time and this didn't happen to me until 4.19rc4
but that could simply be because I didn't turn off the monitors(???).
bisecting will take time.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2337 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-09-24 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-108037-502@http.bugs.freedesktop.org/>
2018-09-24 8:19 ` [Bug 108037] Turning monitors off and on again makes the kernel panic and system freeze bugzilla-daemon
2018-09-24 14:18 ` bugzilla-daemon
2018-09-24 16:46 ` bugzilla-daemon [this message]
2018-09-24 16:47 ` bugzilla-daemon
2018-09-28 20:43 ` bugzilla-daemon
2018-10-02 15:48 ` bugzilla-daemon
2018-10-02 15:53 ` bugzilla-daemon
2018-10-03 0:37 ` bugzilla-daemon
2018-10-08 13:28 ` bugzilla-daemon
2018-11-18 13:48 ` bugzilla-daemon
2019-01-22 16:32 ` bugzilla-daemon
2019-02-04 15:26 ` bugzilla-daemon
2019-04-25 6:52 ` 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-108037-502-ISMw9nvDEP@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.