Hi Jani,
> >> diff --git a/drivers/gpu/drm/i915/intel_uncore.c
> >> b/drivers/gpu/drm/i915/intel_uncore.c
> >> index 796ebfe6c550..9d665978cc43 100644
> >> --- a/drivers/gpu/drm/i915/intel_uncore.c
> >> +++ b/drivers/gpu/drm/i915/intel_uncore.c
> >> @@ -1931,9 +1931,6 @@ unclaimed_reg_debug(struc
On Tue, 11 Jul 2023, Andi Shyti wrote:
> Hi Lee,
>
> I'm really sorry for the late reply, I had some holidays in
> between.
>
> On Tue, Jul 04, 2023 at 04:07:27PM +0800, Lee Shawn C wrote:
>> Perform reboot stresss test on a kernel build with lockdebug flag enabled.
>> Bad unlock balanace detected
Hi Lee,
I'm really sorry for the late reply, I had some holidays in
between.
On Tue, Jul 04, 2023 at 04:07:27PM +0800, Lee Shawn C wrote:
> Perform reboot stresss test on a kernel build with lockdebug flag enabled.
> Bad unlock balanace detected would happened sometimes. Below is the
> problemati
On Tue, 04 Jul 2023, Lee Shawn C wrote:
> Perform reboot stresss test on a kernel build with lockdebug flag enabled.
> Bad unlock balanace detected would happened sometimes. Below is the
> problematic scenario. If params.mmio_debug value was changed at step #4.
> And it would trigger this issue. M
Perform reboot stresss test on a kernel build with lockdebug flag enabled.
Bad unlock balanace detected would happened sometimes. Below is the
problematic scenario. If params.mmio_debug value was changed at step #4.
And it would trigger this issue. Modify code flow that decide to
enable/disable mmi
