Hi Erik, Greg, On Wed, 28 Nov 2018 00:27:37 +0000, Schmauss, Erik wrote: > Here's an additional data point from the discussion on bz201721. > The user started using fancontrol during the period where resource conflict > checking was unintentionally removed. If the reporter tries using fancontrol > on 4.18.13, they report that fancontrol does not work. So it was basically > always the case that he needed to use acpi_resource_conflicts=lax for a short > period of time. > > I understand that this "breaks" this machine but we shouldn't be reverting > resource conflict checking for all other drivers just because of fancontrol. By > removing this check, we are suppressing warnings and changing the loading behavior > of other drivers as well. I agree. The incorrect (or at the very least incomplete and confusing) claims in bug #201721 made me think it was a regression from older versions. As it turns out that this isn't the case, my request to revert 4abb951b73ff0a8a979113ef185651aa3c8da19b from stable kernel series was incorrect. I apologize for the noise and ask Greg to undo the revert. Thanks, -- Jean Delvare SUSE L3 Support
