[Intel-gfx] [REGRESSION 4.19-rc2] sometimes hangs with black screen when resuming from suspend or hibernation (was: Re: Linux 4.19-rc2)

Ville Syrjälä ville.syrjala at linux.intel.com
Wed Sep 12 17:10:20 UTC 2018


On Tue, Sep 11, 2018 at 12:17:05PM +0200, Martin Steigerwald wrote:
> Cc´d Intel Gfx mailing list, in case somebody there knows something:
> 
> Cc´d Thorsten for regression tracking… forgot initially. Can also open 
> bug report at a later time but so far I cannot provide many details 
> about the issue.
> 
> Rafael J. Wysocki - 11.09.18, 10:17:
> > On Tue, Sep 11, 2018 at 10:01 AM Martin Steigerwald 
> <martin at lichtvoll.de> wrote:
> > > Hi.
> > > 
> > > Linus Torvalds - 02.09.18, 23:45:
> > > > As usual, the rc2 release is pretty small. People are taking a
> > > 
> > > With 4.19-rc2 this ThinkPad T520 with i5 Sandybrdige sometimes hangs
> > > with black screen when resuming from suspend or hibernation.  With
> > > 4.18.1 it did not. Of course there have been userspace related
> > > updates that could be related.
> > > 
> > > I currently have no time to dig into this and on this production
> > > laptop I generally do not do bisects between major kernel releases.
> > > So currently I only answer questions that do not require much time
> > > to answer.
> > > 
> > > For now I switched back to 4.18. If that is stable – and thus likely
> > > no userspace component is related –, I go with 4.19-rc3 or whatever
> > > is most recent version to see if the issue has been fixed already.
> > 
> > There were almost no general changes related to system-wide PM between
> > 4.18 and current, so I would suspect one of the device drivers or the
> > x86 core.  It also may be something like CPU online/offline, however.
> 
> I see. I wondered about intel-gfx driver already. Of course it could 
> also be something else.
> 
> I forgot to mention: The mouse pointer was visible, but the screen 
> remained black.

Did the mouse cursor still move or not?

Could also try suspend without any GUI stuff in the way. Or try the
intel ddx instead of the modesetting ddx (assuming that's what
you're using now) and no compositor to rule out GPU hangs killing
the compositor. The intel ddx can also deal with the GPU not
recovering from a hang by switching to software rendering,
whereas modesetting cannot.

Hmm. Also T520 is an optimus laptop maybe? If there's an nvidia
GPU involved it's going to be hard to get anyone to care. Better
switch that off in the BIOS if you haven't already.

-- 
Ville Syrjälä
Intel


More information about the Intel-gfx mailing list