From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108606] Raven Ridge: constant lockups since latest pull from Linus
Date: Thu, 01 Nov 2018 08:21:14 +0000 [thread overview]
Message-ID: <bug-108606-502-1kZPkj1QoJ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108606-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 813 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108606
--- Comment #14 from Samantha McVey <samantham@posteo.net> ---
Wanted to make sure a few things were clear from my last message:
"I tested again and I still get the gpu lockup without these options (this is
without having any commit reverted)."
- Since I was not getting a lockup under either of the cmdline options, I went
back and made sure I could still easily trigger the lockup with no command line
options. I was able to trigger the lockup with no command line options.
The systemd hook:
- This hook is not related to any regression to my knowledge as I've used it
since shortly after I got this laptop, so all of my testing has always had this
suspend hook.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1628 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-11-01 8:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 21:41 [Bug 108606] Raven Ridge: constant lockups since latest pull from Linus bugzilla-daemon
2018-10-30 21:45 ` bugzilla-daemon
2018-10-30 21:50 ` bugzilla-daemon
2018-10-30 22:00 ` bugzilla-daemon
2018-10-31 2:44 ` bugzilla-daemon
2018-10-31 19:07 ` bugzilla-daemon
2018-10-31 19:38 ` bugzilla-daemon
2018-10-31 19:50 ` bugzilla-daemon
2018-10-31 19:52 ` bugzilla-daemon
2018-11-01 2:44 ` bugzilla-daemon
2018-11-01 2:53 ` bugzilla-daemon
2018-11-01 4:27 ` bugzilla-daemon
2018-11-01 5:06 ` bugzilla-daemon
2018-11-01 8:06 ` bugzilla-daemon
2018-11-01 8:21 ` bugzilla-daemon [this message]
2018-11-01 16:53 ` bugzilla-daemon
2018-11-01 17:22 ` bugzilla-daemon
2018-11-20 14:46 ` bugzilla-daemon
2018-11-20 14:48 ` bugzilla-daemon
2019-11-19 9:01 ` 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-108606-502-1kZPkj1QoJ@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.