linux-kernel - Re: Linux 4.4.4 [regression]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <56DD8E3F.8060004@web.de>
Date:	Mon, 7 Mar 2016 15:20:47 +0100
From:	Jörg-Volker Peetz <jvpeetz@....de>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org, stable@...r.kernel.org, lwn@....net,
	Jiri Slaby <jslaby@...e.cz>,
	Alex Deucher <alexander.deucher@....com>
Subject: Re: Linux 4.4.4 [regression]

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@....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@....com>
>> Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.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.