---------- Forwarded message ---------
From:
Gabriel Francisco <frc.gabriel@gmail.com>Date: Thu, Oct 12, 2023 at 8:23 PM
Subject: Re: Bug#1053122: linux-image-6.5.0-1-amd64: using smp_processor_id() in preemptible
To: Ben Hutchings <
ben@decadent.org.uk>
Hi,
> The CPU registers contain several addresses starting ffff89, except for
> rbx which starts ffff99 (and is the faulting address). That looks like
> a single bit got flipped.
Thanks for the explanation! (now I know how to detect bit flips) :D
> The first BUG message should be more meaningful that what comes after.
> This shows the kernel tried to access non-existent memory.
Yes, I should have reported the first one indeed, I thought too much and ended reporting the second one. Sorry about that.
> This could be due to a kernel bug, but is more likely a hardware
> problem. Please test the RAM with memtest86+. Also if you've enabled
> any overclocking options, turn those off.
Even with XMP(3000@1.35v) enabled (F4-3000C16-16GISB), memtest86+ ran for 3 hours and printed PASS in the screen.
I removed the XMP profile from my memories and ordered new rams to check if my current ones are faulty (or not).
The message in dmesg was only one occasion. (but I reported it anyways)
The hang does still happens with/without XMP when running 6.5.x kernel series. It happens when maximizing a video (or time-to-time when my cursor enters the video area) when using kernel 6.5.x. It does not happen with kernel 6.1.x series.
I'm using amgpu module.
Greetings,