Re: [REGRESSSION] on linux-next (next-20250509)

[Rodrigo Vivi <rodrigo.vivi@intel.com>]

On Thu, Jul 03, 2025 at 09:43:41AM -0500, Lucas De Marchi wrote:
> Hi,
> 
> On Wed, May 28, 2025 at 03:07:51PM +0200, Luke Jones wrote:
> > On Wed, 28 May 2025, at 12:08 PM, Borah, Chaitanya Kumar wrote:
> > > Hello Luke,
> > > 
> > > Hope you are doing well. I am Chaitanya from the linux graphics team in Intel.
> > > 
> > > This mail is regarding a regression we are seeing in our CI runs[1] on
> > > linux-next repository.
> > 
> > Can you tell me if the fix here was included?
> > https://lkml.org/lkml/2025/5/24/152
> > 
> > I could change to:
> > static void asus_s2idle_check_register(void)
> > {
> >    // Only register for Ally devices
> >    if (dmi_check_system(asus_rog_ally_device)) {
> >        if (acpi_register_lps0_dev(&asus_ally_s2idle_dev_ops))
> >            pr_warn("failed to register LPS0 sleep handler in asus-wmi\n");
> >    }
> > }
> > 
> > but I don't really understand what is happening here. The inner lps0 functions won't run unless use_ally_mcu_hack is set.
> > 
> > I will do my best to fix but I need to understand what happened a bit better.

Hi Luke, is there anything we could do to help here? Any log or info that
could help from this machine?

This bug is blocking some of our CI runs here.

Thanks,
Rodrigo.

> 
> Any updates here? This is basically killing our tests for drm-xe-fixes
> we are submitting to 6.16 since it taints the kernel. If we can't fix,
> maybe it's already late enough in RCs that we should need a revert?
> 
> FWIW, for 6.17 we have a branch on the side we also merge before testing
> and we've been including the change above to stop it from killing the
> rest of our CI:
> https://gitlab.freedesktop.org/drm/i915/kernel/-/commit/e9d0926aa1c6afcc920013c39d5bd6dd85f581fb
> 
> Lucas De Marchi