Re: latest -git: WARNING: at arch/x86/kernel/ipi.c:123 send_IPI_mask_bitmask+0xc3/0xe0()

[Andi Kleen]

> On some systems (for which there aren't BIOS updates) the trip points are
> set too low.  

There were patches floating to make this configurable. I was always
a little sceptical of them, but they exist.

> If we get a thermal event that was caused by temporary
> increased workload, temperature will drop off again when that workload
> is complete.

But none of the cpufreq governours do this. They only care about
load, not about temperature.

> For sustained workloads we'd get additional thermal events, at which
> time we make a decision "ok, we've throttled as far as we can, and
> things are still going badly, power off".

That is what the ACPI driver does when the trip point is reached.

> In the event of a failed fan or similar, shutting down is obviously
> the right thing to do, and we'd get further thermal events after
> throttling which would allow us to do so.

So you're saying processor_thermal should let the system cook
for some time first before really taking action?

-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/