From: Mike Galbraith <efault@gmx.de>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: LKML <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
David Airlie <airlied@linux.ie>
Subject: Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335
Date: Tue, 11 Jul 2017 20:08:30 +0200 [thread overview]
Message-ID: <1499796510.5315.27.camel@gmx.de> (raw)
In-Reply-To: <CAKb7Uvgh-gj+4dHhDfptLD1Ggz5rwxsG3jBOqQ3h6yxV6_woqg@mail.gmail.com>
On Tue, 2017-07-11 at 13:51 -0400, Ilia Mirkin wrote:
> Some details that may be useful in analysis of the bug:
>
> 1. lspci -nn -d 10de:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1)
01:00.1 Audio device [0403]: NVIDIA Corporation GM204 High Definition Audio Controller [10de:0fbb] (rev a1
> 2. What displays, if any, you have plugged into the NVIDIA board when
> this happens?
A Philips 273V, via DVI.
> 3. Any boot parameters, esp relating to ACPI, PM, or related?
None for those, what's there that will be unfamiliar to you are for
patches that aren't applied.
nortsched hpc_cpusets skew_tick=1 ftrace_dump_on_oops audit=0
nodelayacct cgroup_disable=memory rtkthreads=1 rtworkqueues=2 panic=60
ignore_loglevel crashkernel=256M,high
-Mike
next prev parent reply other threads:[~2017-07-11 18:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 17:32 [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Mike Galbraith
2017-07-11 17:51 ` Ilia Mirkin
2017-07-11 18:08 ` Mike Galbraith [this message]
2017-07-11 18:22 ` Ilia Mirkin
2017-07-11 18:53 ` Mike Galbraith
2017-07-12 7:45 ` Mike Galbraith
2017-07-12 9:55 ` Mike Galbraith
2017-07-12 11:25 ` Mike Galbraith
2017-07-12 11:37 ` Ilia Mirkin
2017-07-12 17:19 ` Mike Galbraith
2017-07-12 19:33 ` Tobias Klausmann
2017-07-14 13:36 ` Mike Galbraith
2017-07-14 13:41 ` Mike Galbraith
2017-07-14 15:05 ` Tobias Klausmann
2017-07-14 15:10 ` [Nouveau] " Karol Herbst
2017-07-14 15:15 ` Mike Galbraith
2017-07-14 15:16 ` Ilia Mirkin
2017-07-14 15:19 ` Tobias Klausmann
2017-07-14 15:20 ` Ilia Mirkin
2017-07-14 15:55 ` Peter Zijlstra
2017-07-14 15:11 ` Mike Galbraith
2017-07-14 15:50 ` Peter Zijlstra
2017-07-14 15:58 ` Mike Galbraith
2017-07-14 16:10 ` Peter Zijlstra
2017-07-14 16:33 ` Mike Galbraith
2017-07-14 19:42 ` Josh Poimboeuf
2017-07-15 2:45 ` Mike Galbraith
2017-07-17 17:20 ` Jessica Yu
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=1499796510.5315.27.camel@gmx.de \
--to=efault@gmx.de \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=imirkin@alum.mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@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