Backlight Regression in i915 that isn't handled appropriately afaics

Backlight Regression in i915 that isn't handled appropriately afaics

[Thorsten Leemhuis]

Hi i915 maintainers, this is your Linux kernel regression tracker!
What's up with the following regression?

https://gitlab.freedesktop.org/drm/intel/-/issues/5284

That report it more than two weeks old now, but seems nothing of
substance happened. And the thing is: the report is older, as the issue
in fact was reported on 2022-01-31 already here:

https://bugzilla.kernel.org/show_bug.cgi?id=215553

After that there was a different ticket about it later here:
https://gitlab.freedesktop.org/drm/intel/-/issues/5027

But it got confusing, so the reporter created the ticket the first link
in this message points to. I fully understand some of the reasons why
this was not handled appropriately, but it looks like even the latest
ticket is mostly ignored, apart from some bug triaging.

So could anybody please take a look into this at at least tell the
reporter what to do to (bisection maybe?) get this solved?

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I'm getting a lot of
reports on my table. I can only look briefly into most of them and lack
knowledge about most of the areas they concern. I thus unfortunately
will sometimes get things wrong or miss something important. I hope
that's not the case here; if you think it is, don't hesitate to tell me
in a public reply, it's in everyone's interest to set the public record
straight.

P.S.S.: for rezgbot:

Link:
https://lore.kernel.org/regressions/74ee2216-a295-c2b6-328b-3e6d0cc1847e@leemhuis.info/

Re: [Intel-gfx] Backlight Regression in i915 that isn't handled appropriately afaics

[Rodrigo Vivi]

On Thu, Mar 24, 2022 at 04:02:41PM +0100, Thorsten Leemhuis wrote:
> Hi i915 maintainers, this is your Linux kernel regression tracker!
> What's up with the following regression?
> 
> https://gitlab.freedesktop.org/drm/intel/-/issues/5284
> 
> That report it more than two weeks old now, but seems nothing of
> substance happened. And the thing is: the report is older, as the issue
> in fact was reported on 2022-01-31 already here:
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=215553
> 
> After that there was a different ticket about it later here:
> https://gitlab.freedesktop.org/drm/intel/-/issues/5027
> 
> But it got confusing, so the reporter created the ticket the first link
> in this message points to. I fully understand some of the reasons why
> this was not handled appropriately, but it looks like even the latest
> ticket is mostly ignored, apart from some bug triaging.
> 
> So could anybody please take a look into this at at least tell the
> reporter what to do to (bisection maybe?) get this solved?
> 
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

Hi Thorsten, thank you so much for your heads up here and I'm sorry for
the delay on the response.

We will ensure this item gets a proper attention.

> 
> P.S.: As the Linux kernel's regression tracker I'm getting a lot of
> reports on my table. I can only look briefly into most of them and lack
> knowledge about most of the areas they concern. I thus unfortunately
> will sometimes get things wrong or miss something important. I hope
> that's not the case here; if you think it is, don't hesitate to tell me
> in a public reply, it's in everyone's interest to set the public record
> straight.
> 
> P.S.S.: for rezgbot:
> 
> Link:
> https://lore.kernel.org/regressions/74ee2216-a295-c2b6-328b-3e6d0cc1847e@leemhuis.info/
> 
>