Subject: Re: Linux 4.4.4 [regression]
To: Greg KH <gregkh@linuxfoundation.org>
References: <20160303233415.GA30194@kroah.com> <56DAB98D.6050305@web.de>
 <20160305174147.GB14401@kroah.com> <56DC2E27.2080006@web.de>
 <20160307011419.GB6588@kroah.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
        torvalds@linux-foundation.org, stable@vger.kernel.org, lwn@lwn.net,
        Jiri Slaby <jslaby@suse.cz>, Alex Deucher <alexander.deucher@amd.com>
Newsgroups: gmane.linux.kernel.stable,gmane.linux.kernel
From: =?UTF-8?Q?J=c3=b6rg-Volker_Peetz?= <jvpeetz@web.de>
Message-ID: <56DD8E3F.8060004@web.de>
Date: Mon, 7 Mar 2016 15:20:47 +0100
MIME-Version: 1.0
In-Reply-To: <20160307011419.GB6588@kroah.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1540
Lines: 43

Greg KH wrote on 03/07/16 02:14:
> On Sun, Mar 06, 2016 at 02:18:31PM +0100, J?rg-Volker Peetz wrote:
>> Greg KH wrote on 03/05/16 18:41:
>>>
>>> Can you use 'git bisect' between 4.4.3 and 4.4.4 to track down the
>>> offending patch?
>>>
>>
>> It's one line of code that freezes X during start on my HP Pavilion dv7 hybrid
>> graphic (AMD HD 42000 - AMD HD 5400):
>>
>> # git bisect visualize
>> commit b36e52c44ce6728824546d8b5f05b844cede96f1
>> Author: Alex Deucher <alexander.deucher@amd.com>
>> Date: Tue Nov 24 14:32:44 2015 -0500
>>
>> drm/radeon: call hpd_irq_event on resume
>>
>> commit dbb17a21c131eca94eb31136eee9a7fe5aff00d9 upstream.
>>
>> Need to call this on resume if displays changes during
>> suspend in order to properly be notified of changes.
>>
>> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>>
>> Removing the line inserted by this patch from 4.4.4 makes X on my laptop work again.
>> Just for the records: with the above patch the laptop freezes during shutdown
>> and has to be switched off by pressing the power button several seconds until
>> power-off.
> 
> Ah, good to know.  Alex, any ideas?
> 
> Also, does this same problem also happen in 4.5-rc7?  If so, that's
> good.  If not, I'm worried that I might have missed a fixup patch
> somewhere.
> 
This same problem with X does happen in 4.5-rc7. And removing the line
introduced by patch b36e52c44ce6728824546d8b5f05b844cede96f1 makes X go again on
my laptop.

Best regards,
jvp.