Hi,
On 27-11-17 11:04, Jean Delvare wrote:
On Sat, 25 Nov 2017 14:43:08 +0100, Hans de Goede wrote:
On 11/24/2017 02:49 PM, Jean Delvare wrote:
Isn't it a BIOS bug?
No, as mentioned in:
The BIOS deliberately does not contain IRQ routing issues because some variants of the Windows driver for this falling over if their is any IRQ routing set, so this is a "feature" not a bug :|
What I do not understand is how Apollo Lake systems are different from any other Intel system, which already had a compatible SMBus controller and apparently having an IRQ configured was never an issue?
I've no answer there I'm afraid.
(...) However if this is considered a BIOS bug then a pr_err(FW_BUG...) would be good to add IMHO.
See above, that would just replace one error message with another on all Apollo Lake systems.
Turning a cryptic error message into a meaningful error message isn't necessarily a bad thing.
Given all the effort distros have done with splash-screens to give users a nice clean boot experience, we really want dmesg --level=err to not print anything unless there is a real problem with either the hardware or the kernel, printing an error message on all Apollo Lake systems is really not helpful IMHO.
Regards,
Hans