On 7/9/23 08:27, Zhang, Rui wrote:
On Sat, 2023-07-08 at 16:17 +0200, Thorsten Leemhuis wrote:
On 07.07.23 12:55, Linux regression tracking (Thorsten Leemhuis)
wrote:
On 07.07.23 10:25, Zhang, Rui wrote:
I run into a NULL pointer dereference and kernel boot hang after
switching to latest upstream kernel, and git bisect shows that
below
commit is the first offending commit, and I have confirmed that
commit
19898ce9cf8a has the issue while 19898ce9cf8a~1 does not.
FWIW, this is the fourth such report about this that I'm aware of.
The first is this one (with two affected users afaics):
https://bugzilla.kernel.org/show_bug.cgi?id=217622
The second is this one:
https://lore.kernel.org/all/CAAJw_Zug6VCS5ZqTWaFSr9sd85k%3DtyPm9DEE%2BmV%3DAKoECZM%2BsQ@xxxxxxxxxxxxxx/
The third:
https://lore.kernel.org/all/9274d9bd3d080a457649ff5addcc1726f08ef5b2.camel@xxxxxxxxxxx/
And in the past few days two people from Fedora land talked to me
on IRC
with problems that in retrospective might be caused by this as
well.
I got confirmation: one of those cases is also caused by 19898ce9cf8a
But I write for a different reason:
Larry (now CCed) looked at the culprit and spotted something that
looked
suspicious to him; he posted a patch and looks for testers:
https://lore.kernel.org/all/0068af47-e475-7e8d-e476-c374e90dff5f@xxxxxxxxxxxx/
I applied this patch but the problem still exists.
thanks,
rui
Rui,
I am not surprised that the patch did not help. I guess you will need to stay
with kernel 6.3.X until the Intel developers return from their summer break.
Larry