[Bug 204807] Hardware monitoring sensor nct6798d doesn't work unless acpi_enforce_resources=lax is enabled

bugzilla-daemon
2022-05-25T21:08:10Z

Denis Pauk (pauk.denis@gmail.com) changed:

What |Removed |Added
----------------------------------------------------------------------------
Attachment #301030|0 |1
is obsolete| |

--- Comment #248 from Denis Pauk (pauk.denis@gmail.com) ---
Created attachment 301047
--> https://bugzilla.kernel.org/attachment.cgi?id=301047&action=edit
Asus WMI for nct6775 v5.18 base (2022.05.25)

(In reply to Sven Arvidsson from comment #247)
> Created attachment 301046 [details]
> Z170M-PLUS crash
>
> (In reply to Denis Pauk from comment #245)
> > I have made mistake in board name(Z170-PLUS instead Z170M-PLUS), could you
> > please recheck with rebased patch?
> Thanks for the new patch! The chip is detected now, but unfortunately
> crashes after loading.
>
> Crash log is attached.
Welcome! I have added small fix for init, could you please try?

(In reply to Rob Miller from comment #246)
> (In reply to Denis Pauk from comment #240)
> > Created attachment 300963 [details]
> > Asus WMI for nct6775 v5.17 base (2022.05.15)
> >
> > (In reply to Rob Miller from comment #239)
> > > Created attachment 300958 [details]
> > > Asus Z170-DELUXE dump
>
> > Unfortunately, your motherboard does not have any endpoints supported by
> > upstreamed drivers.
> >
> > Could you please try with attached patch? It provides custom lock method
> > that is unsupported by upstream driver.
>
> Thank you for your continued efforts on this.
>
> I installed the 5.18 base patch and was able to boot without the warning
> messages.
>
> The nct6775 module loaded without issue, but 'sensors' command did not show
> all the info for my device as it does booting the Ubuntu 5.15.0-33-generic
> kernel with the 'acpi_enforce_resources=lax' option.
>
> nct675 reports: Found NCT6793D or compatible chip at 0x2e:0x290

Welcome! I have added little more debug information and additional check for
different name of mutex. could you please try?

Other possible issue can be different naming of vendor: "ASUSTeK COMPUTER INC."
vs "ASUSTeK Computer INC.".