9.1 callout behavior

[Alexander Motin]

On 10.12.2013 17:12, Bret Ketchum wrote:
>      Do either of you have a dual socket/package motherboard to play
> with? I've tried a couple single socket motherboards and cannot
> reproduce the issue. I'm wondering if this occurs on only multi-socket
> mobos.

My main test system is dual-socket (Supermicro X8DTU).

> On Fri, Dec 6, 2013 at 12:55 PM, Adrian Chadd <adrian at freebsd.org
> <mailto:adrian at freebsd.org>> wrote:
>
>     Remember that I have such similar stupid behaviour with my three year
>     old Atom laptop. I promise I'll bring it along to the next freebsd
>     event you're at. :P
>
>
>     -adrian
>
>     On 6 December 2013 10:43, Alexander Motin <mav at freebsd.org
>     <mailto:mav at freebsd.org>> wrote:
>      > On 06.12.2013 20:35, Adrian Chadd wrote:
>      >>
>      >> On 6 December 2013 03:43, Alexander Motin <mav at freebsd.org
>     <mailto:mav at freebsd.org>> wrote:
>      >>>
>      >>> On 06.12.2013 13:41, Bret Ketchum wrote:
>      >>>>
>      >>>>
>      >>>>       Any luck in recreating?
>      >>>
>      >>>
>      >>>
>      >>> Nope. I've tried with and without deep C-states enabled and
>     still no any
>      >>> error messages on console.
>      >>
>      >>
>      >> Are you trying it with the exact same hardware?
>      >
>      >
>      > No. We found that while both of my test machines active now has
>     C-state
>      > invariant LAPIC, at least one of Bret's is not. But that doesn't
>     really
>      > explain much because C-states there are not visually enabled
>     either by OS,
>      > or via C1E by BIOS.
>      >
>      >
>      >> For both of you - is HT on/off?
>      >
>      >
>      > Both if my systems have HTT active.
>      >
>      > --
>      > Alexander Motin
>
>


-- 
Alexander Motin