[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <547c4c61-26af-ee0d-146f-d0db077dc53f@leemhuis.info>
Date: Mon, 15 May 2023 18:43:27 +0200
From: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: Bagas Sanjaya <bagasdotme@...il.com>,
Hans de Goede <hdegoede@...hat.com>,
Linux Regressions <regressions@...ts.linux.dev>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Wireless <linux-wireless@...r.kernel.org>,
Broadcom 80211 Devices <brcm80211-dev-list.pdl@...adcom.com>,
SHA cyfmac Subsystem <SHA-cyfmac-dev-list@...ineon.com>,
Linux Kernel Network Developers <netdev@...r.kernel.org>
Cc: Hante Meuleman <hante.meuleman@...adcom.com>,
Pieter-Paul Giesberts <pieter-paul.giesberts@...adcom.com>,
Franky Lin <franky.lin@...adcom.com>,
Arend van Spriel <arend.vanspriel@...adcom.com>,
Kalle Valo <kvalo@...nel.org>, julien.falque@...il.com
Subject: Re: Fwd: Freeze after resuming from hibernation (culprit is brcmfmac
change?)
On 15.05.23 15:09, Bagas Sanjaya wrote:
> On 5/15/23 15:56, Hans de Goede wrote:
>> On 5/15/23 04:21, Bagas Sanjaya wrote:
>>> I notice a regression report on bugzilla [1]. Quoting from it:
> [...]
>>>> A bisect on linux-git gave commit da6d9c8ecd00 as the cause of the problem.
>>
>> da6d9c8ecd00e2 is known to cause a NULL pointer deref on resume,
Bagas, fwiw, to prevent situations like these I usually search on lore
for a shorted variant of the commit-id[1] before telling regzbot about
it. In quite a lot of cases I find something useful that might mean that
tracking is not worth it.
Ciao, Thorsten
e.g. [1] https://lore.kernel.org/all/?q=da6d9c8*
Powered by blists - more mailing lists