Date: Tue, 10 Dec 2013 17:23:41 +0200 From: Alexander Motin <mav@FreeBSD.org> To: Bret Ketchum <bcketchum@gmail.com>, Adrian Chadd <adrian@freebsd.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: 9.1 callout behavior Message-ID: <52A731FD.8060307@FreeBSD.org> In-Reply-To: <CAGm6yaRd41fXsFF1OTFyLQq7LAsbnZQ934-zYXNFsuCGCaMQqQ@mail.gmail.com> References: <CAGm6yaTEFECTYVb94A13TaXMPSLtKLpTbw4iNdgd8SuNF1QDaA@mail.gmail.com> <CAJ-Vmokrchy4pXLvZ21sCV09fQUdYKeUYCEH1U1NdfDBxhyJQg@mail.gmail.com> <5295A261.2060403@FreeBSD.org> <CAGm6yaRAPoiVXuv3HgvJCHBTUYGokLyRLb_n0MQEyRp%2BcJUrqA@mail.gmail.com> <CAGm6yaRRcS1e5b_uo4wq=ArSMxFuuTkrKTgOTcQC9nbLnYi6Yw@mail.gmail.com> <529F4409.9080403@FreeBSD.org> <CAGm6yaRFQZ69gQ_Jv0JG5-ru=XtROV5mz7kONC46LRYoe1XTVg@mail.gmail.com> <CAJ-VmonJg-Lsbijc1PnqKt%2BAfmjLxkQpXbKQ4R90bWq7QoXkJQ@mail.gmail.com> <CAGm6yaT=6b6AxDxgivP1jUBmNG1Ynrh58tvhhtZ-qW%2BMKpbj3w@mail.gmail.com> <CAGm6yaSQBVXEQ=8NNLjQ0-1q5jxpBeQT2GCUhhCa4_qqiPX=pQ@mail.gmail.com> <52A1B869.6080407@FreeBSD.org> <CAJ-VmokdyubZLWfp7jub6LqCT%2BZwx0bO4vL6_G3L7CNngcYkQA@mail.gmail.com> <52A21AE9.5020803@FreeBSD.org> <CAJ-VmomRfSG7rXxKMEummRWET1bn_JZ=E7uG-Q1n-_H5NB-r5g@mail.gmail.com> <CAGm6yaRd41fXsFF1OTFyLQq7LAsbnZQ934-zYXNFsuCGCaMQqQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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@freebsd.org > <mailto:adrian@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@freebsd.org > <mailto:mav@freebsd.org>> wrote: > > On 06.12.2013 20:35, Adrian Chadd wrote: > >> > >> On 6 December 2013 03:43, Alexander Motin <mav@freebsd.org > <mailto:mav@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52A731FD.8060307>