Hello, I've noticed there are a lot of bugs filed against Ubuntu due to the changes that introduced strict resource checking between the acpi driver and legacy hardware monitor drivers [1]. Although I understand the reason for the strict checking, the legacy drivers seemed to work fine. I'm unaware of any real issues that were caused by using them. Thus, I'm wondering if it would be worthwhile to whitelist machines that are known to work OK even with the resources being doubly held by both the acpi driver and a legacy driver. It certainly does not seem prudent to set acpi_enforce_resources=lax across the board, but the change to strict resource checking seems to have done more harm than good for the average user. I noticed a similar thread at [2]. At the end it was proposed that a whitelist be set up to handle this issue. Has anyone been working on this? Beyond the potential breakage of function, I'm also concerned by the logging level of the message that informs the user of the resource contention. Right now, KERN_ERR is used by default when a contention is found. Basically, the message means "You tried to use a legacy driver, but that's not a good idea, so I've prevented you from doing so." It seems ok on the one hand to call this an error condition. On the other hand, it pollutes Ubuntu's startup screen because it thinks there's a real error occurring in the kernel. From this point of reference, it seems better to emit the message at the KERN_WARN level at all times, since it's not really something that a user should be frightened of when they see their computer spit out such a message at boot. Any thoughts on these two ideas? I can work on some patches if either is deemed worthwhile. Thanks, Chase Douglas [1] https://launchpad.net/+search?field.text=acpi_enforce_resources&field.actions.search=Search [2] http://marc.info/?l=linux-acpi&m=125233061012344&w=2 -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
