public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Lyude Paul <lyude@redhat.com>
To: Takashi Iwai <tiwai@suse.de>, intel-gfx@lists.freedesktop.org
Subject: Re: Panic after S3 resume and modeset with MST
Date: Mon, 27 Mar 2017 18:14:55 -0400	[thread overview]
Message-ID: <1490652895.820.0.camel@redhat.com> (raw)
In-Reply-To: <s5hk27an1x6.wl-tiwai@suse.de>

Hi! Just an FYI I am planning on taking a look at this very soon

On Mon, 2017-03-27 at 18:02 +0200, Takashi Iwai wrote:
> Hi,
> 
> the upstream fix a16b7658f4e0d4aec9bc3e75a5f0cc3f7a3a0422
>     drm/i915: Call intel_dp_mst_resume() before resuming displays
> 
> seems to trigger a kernel panic when some modeset change happens
> after
> S3 resume.  The details are found in openSUSE bugzilla,
>   https://bugzilla.suse.com/show_bug.cgi?id=1029634
> 
> In short, the following procedure causes a kernel panic (supposedly)
> almost 100% on Dell Latitude with Skylake with MST DP on dock:
> 
> - Boot with a docking station, DP-1 connected.
> - Login on X
> - xrandr --output eDP-1 --primary --auto --output DP-1-1 --auto --
> left-of eDP-1
>   ==> This changes the mode.
> - Suspend ("systemctl suspend" in my case), and close the lid.
> - Remove from the dock (keep the lid closed).
> - Open the lid, which resumes automatically.  It works.
> - Suspend again.
> - Connect to the dock again (keep the lid closed).
> - Open the lid, which resumes automatically.  It's still OK.
> - xrandr --output eDP-1 --primary --auto --output DP-1-1 --auto --
> left-of eDP-1
>   ==> Now the kernel feezes.
> 
> Reverting the commit mentioned above fixes the problem.
> 
> The problem is present in all versions I tested.  The reported kernel
> in the Bugzilla is 4.4.x-based one, but the issue is seen in 4.11-
> rc3,
> too.  Note that the S3 resume itself works in 4.11-rc3; the kernel
> panic happens when invoking xrandr manually after that.
> 
> Unfortunately, I couldn't get a kernel panic message, so far.  kdump
> didn't work well in this case by some reason.  There are some
> screenshots taken by the original reporter (could switch VT
> beforehand), but I don't know whether it helps.
> 
> If you have any hints for further debugging, it'd be highly
> appreciated.
> 
> 
> thanks,
> 
> Takashi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-03-27 22:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 16:02 Panic after S3 resume and modeset with MST Takashi Iwai
2017-03-27 22:14 ` Lyude Paul [this message]
2017-03-29 13:10 ` Takashi Iwai
2017-03-29 13:34   ` Ville Syrjälä
2017-03-29 13:54     ` Takashi Iwai
2017-03-30  0:24       ` Lyude Paul
2017-03-30  5:55         ` Takashi Iwai
2017-03-30 18:07           ` Lyude Paul
2017-03-30 18:50             ` Takashi Iwai
2017-03-30 20:01               ` Lyude Paul
2017-03-30 20:27                 ` Takashi Iwai

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=1490652895.820.0.camel@redhat.com \
    --to=lyude@redhat.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tiwai@suse.de \
    /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