linux-kernel - Re: [git pull] drm for 6.10-rc1

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: <0631afa1-952b-4fe6-9597-e870d315af19@amd.com>
Date: Thu, 16 May 2024 11:53:20 +0530
From: "Paneer Selvam, Arunpravin" <arunpravin.paneerselvam@....com>
To: Dave Airlie <airlied@...il.com>,
 Linus Torvalds <torvalds@...ux-foundation.org>,
 "Deucher, Alexander" <Alexander.Deucher@....com>
Cc: Christian König <christian.koenig@....com>,
 Matthew Auld <matthew.auld@...el.com>, Daniel Vetter
 <daniel.vetter@...ll.ch>, dri-devel <dri-devel@...ts.freedesktop.org>,
 LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm for 6.10-rc1



On 5/16/2024 8:12 AM, Dave Airlie wrote:
> On Thu, 16 May 2024 at 10:06, Dave Airlie <airlied@...il.com> wrote:
>> On Thu, 16 May 2024 at 09:50, Dave Airlie <airlied@...il.com> wrote:
>>> On Thu, 16 May 2024 at 06:29, Linus Torvalds
>>> <torvalds@...ux-foundation.org> wrote:
>>>> On Wed, 15 May 2024 at 13:24, Linus Torvalds
>>>> <torvalds@...ux-foundation.org> wrote:
>>>>> I have to revert both
>>>>>
>>>>>    a68c7eaa7a8f ("drm/amdgpu: Enable clear page functionality")
>>>>>    e362b7c8f8c7 ("drm/amdgpu: Modify the contiguous flags behaviour")
>>>>>
>>>>> to make things build cleanly. Next step: see if it boots and fixes the
>>>>> problem for me.
>>>> Well, perhaps not surprisingly, the WARN_ON() no longer triggers with
>>>> this, and everything looks fine.
>>>>
>>>> Let's see if the machine ends up being stable now. It took several
>>>> hours for the "scary messages" state to turn into the "hung machine"
>>>> state, so they *could* have been independent issues, but it seems a
>>>> bit unlikely.
>>> I think that should be fine to do for now.
>>>
>>> I think it is also fine to do like I've attached, but I'm not sure if
>>> I'd take that chance.
>> Scrap that idea, doesn't die, but it makes my system unhappy, like
>> fbdev missing,
>>
>> so for quickest path forward, just make the two reverts seems best.
>>
>> I've reproduced it here, so I'll track it down,
> https://lore.kernel.org/amd-gfx/20240514145636.16253-1-Arunpravin.PaneerSelvam@amd.com/T/#t
>
> This patch seems to fix it for me, I might just pull it into my tree
> and send it to you.
Sorry for the noise, Dave's link is the right fix for this issue. Have 
you already picked it up or should I push it to
drm-misc-next-fixes?

Thanks,
Arun.
>
> Dave.