Ian Smith wrote: > So not looking much like overheating. But don't these messages requoted > below seem at all significant? At least, I've never seen them before: > >> est0: <Enhanced SpeedStep Frequency Control> on cpu0 >> est0: Invalid id16 (set, cur) = (20, 21) >> est0: Can't check freq 2667, it may be invalid >> est0: Invalid id16 (set, cur) = (19, 21) >> est0: Can't check freq 2533, it may be invalid >> est0: Invalid id16 (set, cur) = (18, 21) >> est0: Can't check freq 2400, it may be invalid >> est0: Invalid id16 (set, cur) = (17, 21) >> est0: Can't check freq 2267, it may be invalid >> est0: Invalid id16 (set, cur) = (16, 21) >> est0: Can't check freq 2133, it may be invalid >> est0: Invalid id16 (set, cur) = (15, 21) >> est0: Can't check freq 2000, it may be invalid >> est0: Invalid id16 (set, cur) = (14, 21) >> est0: Can't check freq 1867, it may be invalid >> est0: Invalid id16 (set, cur) = (13, 21) >> est0: Can't check freq 1733, it may be invalid >> est0: Invalid id16 (set, cur) = (12, 21) >> est0: Can't check freq 1600, it may be invalid
They are not. It is specifics of EIST behavior on multicore CPUs. It is impossible to test P-states during driver attach (before AP CPUs started). I have already disabled this check for SMP systems. -- Alexander Motin _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
