On 23-12-2016 22:07, Slawa Olhovchenkov wrote:
> On Fri, Dec 23, 2016 at 09:37:40PM +0100, Willem Jan Withagen wrote:
>
>> On 23-12-2016 20:30, Slawa Olhovchenkov wrote:
>>> On Fri, Dec 23, 2016 at 08:16:39PM +0100, Willem Jan Withagen wrote:
>>>
On 23-12-2016 14:26, Slawa Olhovchenkov
On Fri, Dec 23, 2016 at 09:37:40PM +0100, Willem Jan Withagen wrote:
> On 23-12-2016 20:30, Slawa Olhovchenkov wrote:
> > On Fri, Dec 23, 2016 at 08:16:39PM +0100, Willem Jan Withagen wrote:
> >
> >> On 23-12-2016 14:26, Slawa Olhovchenkov wrote:
> >>> On Thu, Dec 22, 2016 at 09:26:02PM +0100,
On 23-12-2016 20:30, Slawa Olhovchenkov wrote:
> On Fri, Dec 23, 2016 at 08:16:39PM +0100, Willem Jan Withagen wrote:
>
>> On 23-12-2016 14:26, Slawa Olhovchenkov wrote:
>>> On Thu, Dec 22, 2016 at 09:26:02PM +0100, Willem Jan Withagen wrote:
>>>
On 16-12-2016 00:57, Adrian Chadd wrote:
On Fri, Dec 23, 2016 at 08:16:39PM +0100, Willem Jan Withagen wrote:
> On 23-12-2016 14:26, Slawa Olhovchenkov wrote:
> > On Thu, Dec 22, 2016 at 09:26:02PM +0100, Willem Jan Withagen wrote:
> >
> >> On 16-12-2016 00:57, Adrian Chadd wrote:
> >>> heh, an updated BIOS that solves the problem will
On 23-12-2016 14:26, Slawa Olhovchenkov wrote:
> On Thu, Dec 22, 2016 at 09:26:02PM +0100, Willem Jan Withagen wrote:
>
>> On 16-12-2016 00:57, Adrian Chadd wrote:
>>> heh, an updated BIOS that solves the problem will solve the problem. :)
>>>
>>> I think you have enough information to provide to
On Thu, Dec 22, 2016 at 09:26:02PM +0100, Willem Jan Withagen wrote:
> On 16-12-2016 00:57, Adrian Chadd wrote:
> > heh, an updated BIOS that solves the problem will solve the problem. :)
> >
> > I think you have enough information to provide to supermicro. Ie,
> > "SMAP says X, when physical
On 16-12-2016 00:57, Adrian Chadd wrote:
> heh, an updated BIOS that solves the problem will solve the problem. :)
>
> I think you have enough information to provide to supermicro. Ie,
> "SMAP says X, when physical memory pages at addresses X are accessed,
> they don't behave like memory, maybe
Hi,
On 12/21/2016 06:58, Konstantin Belousov wrote:
> What is the exact version of the kernel you are running and which hangs ?
Right now I'm running r310303, booted with SMP disabled.
> Try to bisect.
>
The issue appeared without updating the OS, but I have since updated.
That said, I have
On Tue, Dec 20, 2016 at 04:49:29PM -0500, Steve Wills wrote:
> Hi,
>
> On 12/16/2016 16:20, John Baldwin wrote:
> > On Thursday, December 15, 2016 03:57:58 PM Adrian Chadd wrote:
> >> heh, an updated BIOS that solves the problem will solve the problem. :)
> >>
> >> I think you have enough
Hi,
On 12/16/2016 16:20, John Baldwin wrote:
> On Thursday, December 15, 2016 03:57:58 PM Adrian Chadd wrote:
>> heh, an updated BIOS that solves the problem will solve the problem. :)
>>
>> I think you have enough information to provide to supermicro. Ie,
>> "SMAP says X, when physical memory
On Thursday, December 15, 2016 03:57:58 PM Adrian Chadd wrote:
> heh, an updated BIOS that solves the problem will solve the problem. :)
>
> I think you have enough information to provide to supermicro. Ie,
> "SMAP says X, when physical memory pages at addresses X are accessed,
> they don't
heh, an updated BIOS that solves the problem will solve the problem. :)
I think you have enough information to provide to supermicro. Ie,
"SMAP says X, when physical memory pages at addresses X are accessed,
they don't behave like memory, maybe something is wrong".
All I can think of is some
On Thu, Dec 15, 2016 at 03:56:56PM +0200, Konstantin Belousov wrote:
> > > Possibly, the dmesg of the boot (with late_console=0) with this and only
> > > this patch applied against stock HEAD. This might be long.
> >
> > Do you need all (262144?) lines?
> >
> > Testing system
> >
On Thu, Dec 15, 2016 at 04:16:24PM +0300, Slawa Olhovchenkov wrote:
> On Thu, Dec 15, 2016 at 02:33:30PM +0200, Konstantin Belousov wrote:
>
> > On Thu, Dec 15, 2016 at 01:51:18PM +0300, Slawa Olhovchenkov wrote:
> > > On Wed, Dec 14, 2016 at 09:03:49PM +0200, Konstantin Belousov wrote:
> > >
>
On Thu, Dec 15, 2016 at 02:33:30PM +0200, Konstantin Belousov wrote:
> On Thu, Dec 15, 2016 at 01:51:18PM +0300, Slawa Olhovchenkov wrote:
> > On Wed, Dec 14, 2016 at 09:03:49PM +0200, Konstantin Belousov wrote:
> >
> > > So my opinion did not changed, this sounds like firmware problem.
> > > I
On Thu, Dec 15, 2016 at 01:51:18PM +0300, Slawa Olhovchenkov wrote:
> On Wed, Dec 14, 2016 at 09:03:49PM +0200, Konstantin Belousov wrote:
>
> > So my opinion did not changed, this sounds like firmware problem.
> > I do not see how can I drill into it more.
>
> I am don't know how it related.
On Wed, Dec 14, 2016 at 09:03:49PM +0200, Konstantin Belousov wrote:
> So my opinion did not changed, this sounds like firmware problem.
> I do not see how can I drill into it more.
I am don't know how it related. msgbufp mapped different with and w/o
memory test:
w/o memory test, hang:
On 14/12/16 13:48, Slawa Olhovchenkov wrote:
> On Wed, Dec 14, 2016 at 09:43:24PM +0200, Konstantin Belousov wrote:
>
>> On Wed, Dec 14, 2016 at 10:29:43PM +0300, Slawa Olhovchenkov wrote:
>>> On Wed, Dec 14, 2016 at 09:03:49PM +0200, Konstantin Belousov wrote:
>>>
On Wed, Dec 14, 2016 at
On Wed, Dec 14, 2016 at 09:43:24PM +0200, Konstantin Belousov wrote:
> On Wed, Dec 14, 2016 at 10:29:43PM +0300, Slawa Olhovchenkov wrote:
> > On Wed, Dec 14, 2016 at 09:03:49PM +0200, Konstantin Belousov wrote:
> >
> > > On Wed, Dec 14, 2016 at 06:26:27PM +0300, Slawa Olhovchenkov wrote:
> > >
On Wed, Dec 14, 2016 at 10:29:43PM +0300, Slawa Olhovchenkov wrote:
> On Wed, Dec 14, 2016 at 09:03:49PM +0200, Konstantin Belousov wrote:
>
> > On Wed, Dec 14, 2016 at 06:26:27PM +0300, Slawa Olhovchenkov wrote:
> > > For test hardware setup (NUMA+interleave), what ISO I can try to boot?
> >
On Wed, Dec 14, 2016 at 09:03:49PM +0200, Konstantin Belousov wrote:
> On Wed, Dec 14, 2016 at 06:26:27PM +0300, Slawa Olhovchenkov wrote:
> > On Wed, Dec 14, 2016 at 03:13:36PM +0300, Slawa Olhovchenkov wrote:
> >
> > > On Wed, Dec 14, 2016 at 01:39:27PM +0200, Konstantin Belousov wrote:
> > >
On Wed, Dec 14, 2016 at 06:26:27PM +0300, Slawa Olhovchenkov wrote:
> On Wed, Dec 14, 2016 at 03:13:36PM +0300, Slawa Olhovchenkov wrote:
>
> > On Wed, Dec 14, 2016 at 01:39:27PM +0200, Konstantin Belousov wrote:
> >
> > > In other words, it is almost certainly the hang and not a fault causing
>
On Wed, Dec 14, 2016 at 03:13:36PM +0300, Slawa Olhovchenkov wrote:
> On Wed, Dec 14, 2016 at 01:39:27PM +0200, Konstantin Belousov wrote:
>
> > In other words, it is almost certainly the hang and not a fault causing
> > hang. This means that the machine is not compliant with the IA32
> >
On Wed, Dec 14, 2016 at 04:40:33PM +0200, Konstantin Belousov wrote:
> On Wed, Dec 14, 2016 at 03:13:36PM +0300, Slawa Olhovchenkov wrote:
> > On Wed, Dec 14, 2016 at 01:39:27PM +0200, Konstantin Belousov wrote:
> >
> > > In other words, it is almost certainly the hang and not a fault causing
>
On Wed, Dec 14, 2016 at 03:13:36PM +0300, Slawa Olhovchenkov wrote:
> On Wed, Dec 14, 2016 at 01:39:27PM +0200, Konstantin Belousov wrote:
>
> > In other words, it is almost certainly the hang and not a fault causing
> > hang. This means that the machine is not compliant with the IA32
> >
On Wed, Dec 14, 2016 at 01:39:27PM +0200, Konstantin Belousov wrote:
> In other words, it is almost certainly the hang and not a fault causing
> hang. This means that the machine is not compliant with the IA32
> architecture, in particular, the region reported as normal memory by
> E820 BIOS
On Wed, Dec 14, 2016 at 01:52:11PM +0300, Slawa Olhovchenkov wrote:
> Booting...
> KDB: debugger backends: ddb
> KDB: current backend: ddb
> SMAP type=01 base= len=00099c00
> SMAP type=02 base=00099c00 len=6400
> SMAP type=02 base=000e
On Wed, Dec 14, 2016 at 12:27:11PM +0200, Konstantin Belousov wrote:
> On Wed, Dec 14, 2016 at 11:53:50AM +0200, Konstantin Belousov wrote:
> > On Tue, Dec 13, 2016 at 08:43:45PM +0300, Slawa Olhovchenkov wrote:
> > > On Tue, Dec 13, 2016 at 07:25:29PM +0200, Konstantin Belousov wrote:
> > >
> >
On Wed, Dec 14, 2016 at 11:53:50AM +0200, Konstantin Belousov wrote:
> On Tue, Dec 13, 2016 at 08:43:45PM +0300, Slawa Olhovchenkov wrote:
> > On Tue, Dec 13, 2016 at 07:25:29PM +0200, Konstantin Belousov wrote:
> >
> > > This is not what I expected.
> > > Also, I realized that I mis-read the
On Tue, Dec 13, 2016 at 08:43:45PM +0300, Slawa Olhovchenkov wrote:
> On Tue, Dec 13, 2016 at 07:25:29PM +0200, Konstantin Belousov wrote:
>
> > This is not what I expected.
> > Also, I realized that I mis-read the memory test code. It does not
> > obliterate memory, old content is preserved.
>
On Tue, Dec 13, 2016 at 07:25:29PM +0200, Konstantin Belousov wrote:
> This is not what I expected.
> Also, I realized that I mis-read the memory test code. It does not
> obliterate memory, old content is preserved.
>
> Please do exactly the same testing with another patch, at the end of the
>
On Tue, Dec 13, 2016 at 06:28:38PM +0300, Slawa Olhovchenkov wrote:
> On Tue, Dec 13, 2016 at 05:01:39PM +0200, Konstantin Belousov wrote:
> KDB: debugger backends: ddb
> KDB: current backend: ddb
> SMAP type=01 base= len=00099c00
> SMAP type=02 base=00099c00
On Tue, Dec 13, 2016 at 05:01:39PM +0200, Konstantin Belousov wrote:
> > KDB: debugger backends: ddb
> > KDB: current backend: ddb
> > SMAP type=01 base= len=00099c00
> > SMAP type=02 base=00099c00 len=6400
> > SMAP type=02 base=000e
On Tue, Dec 13, 2016 at 05:34:01PM +0300, Slawa Olhovchenkov wrote:
> On Tue, Dec 13, 2016 at 05:11:14PM +0300, Slawa Olhovchenkov wrote:
>
> > On Tue, Dec 13, 2016 at 03:57:59PM +0200, Konstantin Belousov wrote:
> >
> > > On Tue, Dec 13, 2016 at 03:49:32PM +0300, Slawa Olhovchenkov wrote:
> > >
On Tue, Dec 13, 2016 at 05:11:14PM +0300, Slawa Olhovchenkov wrote:
> On Tue, Dec 13, 2016 at 03:57:59PM +0200, Konstantin Belousov wrote:
>
> > On Tue, Dec 13, 2016 at 03:49:32PM +0300, Slawa Olhovchenkov wrote:
> > > > Boot with NUMA enabled and interleave off.
> > >
> > > Already with
On Tue, Dec 13, 2016 at 03:57:59PM +0200, Konstantin Belousov wrote:
> On Tue, Dec 13, 2016 at 03:49:32PM +0300, Slawa Olhovchenkov wrote:
> > > Boot with NUMA enabled and interleave off.
> >
> > Already with patched kernel
> >
> > > Patch kernel with the 'if (1 || ...)' patch.
> > > Reboot,
On Tue, Dec 13, 2016 at 03:49:32PM +0300, Slawa Olhovchenkov wrote:
> > Boot with NUMA enabled and interleave off.
>
> Already with patched kernel
>
> > Patch kernel with the 'if (1 || ...)' patch.
> > Reboot, enter BIOS setup and enable interleave there.
> > Try to boot - does it boot ?
>
>
On Tue, Dec 13, 2016 at 01:23:40PM +0200, Konstantin Belousov wrote:
> On Tue, Dec 13, 2016 at 02:14:37PM +0300, Slawa Olhovchenkov wrote:
> > On Tue, Dec 13, 2016 at 01:05:35PM +0200, Konstantin Belousov wrote:
> >
> > > On Tue, Dec 13, 2016 at 02:37:14AM +0300, Slawa Olhovchenkov wrote:
> > >
On Tue, Dec 13, 2016 at 02:14:37PM +0300, Slawa Olhovchenkov wrote:
> On Tue, Dec 13, 2016 at 01:05:35PM +0200, Konstantin Belousov wrote:
>
> > On Tue, Dec 13, 2016 at 02:37:14AM +0300, Slawa Olhovchenkov wrote:
> > > On Mon, Dec 12, 2016 at 04:20:33PM -0600, A. Wilcox wrote:
> > >
> > > >
On Tue, Dec 13, 2016 at 01:05:35PM +0200, Konstantin Belousov wrote:
> On Tue, Dec 13, 2016 at 02:37:14AM +0300, Slawa Olhovchenkov wrote:
> > On Mon, Dec 12, 2016 at 04:20:33PM -0600, A. Wilcox wrote:
> >
> > > Try the debugging patch below, which unconditionally disables import
> > >
On Tue, Dec 13, 2016 at 02:37:14AM +0300, Slawa Olhovchenkov wrote:
> On Mon, Dec 12, 2016 at 04:20:33PM -0600, A. Wilcox wrote:
>
> > Try the debugging patch below, which unconditionally disables import of
> > previous buffer. To test, you would need to boot, then frob options in
> >
On Mon, Dec 12, 2016 at 04:20:33PM -0600, A. Wilcox wrote:
> Try the debugging patch below, which unconditionally disables import of
> previous buffer. To test, you would need to boot, then frob options in
> BIOS, reboot, again frob etc.
> >>>
> >>> still need test patch? if yes,
Try the debugging patch below, which unconditionally disables import of
previous buffer. To test, you would need to boot, then frob options in
BIOS, reboot, again frob etc.
>>>
>>> still need test patch? if yes, with BIOS options?
>> Yes, please test the patch. I explained the
On Mon, Dec 12, 2016 at 08:36:47PM +0200, Konstantin Belousov wrote:
> On Mon, Dec 12, 2016 at 08:43:11PM +0300, Slawa Olhovchenkov wrote:
> > On Mon, Dec 12, 2016 at 07:24:18PM +0200, Konstantin Belousov wrote:
> >
> > > On Mon, Dec 12, 2016 at 08:16:34PM +0300, Slawa Olhovchenkov wrote:
> > >
On Mon, Dec 12, 2016 at 08:43:11PM +0300, Slawa Olhovchenkov wrote:
> On Mon, Dec 12, 2016 at 07:24:18PM +0200, Konstantin Belousov wrote:
>
> > On Mon, Dec 12, 2016 at 08:16:34PM +0300, Slawa Olhovchenkov wrote:
> > > On Mon, Dec 12, 2016 at 06:54:57PM +0200, Konstantin Belousov wrote:
> > >
>
On Mon, Dec 12, 2016 at 07:24:18PM +0200, Konstantin Belousov wrote:
> On Mon, Dec 12, 2016 at 08:16:34PM +0300, Slawa Olhovchenkov wrote:
> > On Mon, Dec 12, 2016 at 06:54:57PM +0200, Konstantin Belousov wrote:
> >
> > > On Mon, Dec 12, 2016 at 07:21:53PM +0300, Slawa Olhovchenkov wrote:
> > >
On Mon, Dec 12, 2016 at 08:16:34PM +0300, Slawa Olhovchenkov wrote:
> On Mon, Dec 12, 2016 at 06:54:57PM +0200, Konstantin Belousov wrote:
>
> > On Mon, Dec 12, 2016 at 07:21:53PM +0300, Slawa Olhovchenkov wrote:
> > > On Mon, Dec 12, 2016 at 04:54:18PM +0200, Konstantin Belousov wrote:
> > >
>
On Mon, Dec 12, 2016 at 06:54:57PM +0200, Konstantin Belousov wrote:
> On Mon, Dec 12, 2016 at 07:21:53PM +0300, Slawa Olhovchenkov wrote:
> > On Mon, Dec 12, 2016 at 04:54:18PM +0200, Konstantin Belousov wrote:
> >
> > > On Sun, Dec 11, 2016 at 11:47:09PM +0300, Slawa Olhovchenkov wrote:
> > >
On Mon, Dec 12, 2016 at 07:21:53PM +0300, Slawa Olhovchenkov wrote:
> On Mon, Dec 12, 2016 at 04:54:18PM +0200, Konstantin Belousov wrote:
>
> > On Sun, Dec 11, 2016 at 11:47:09PM +0300, Slawa Olhovchenkov wrote:
> > > Booting...
> > > ESC[01;00H8+0x8+0xe9bdc]
On Mon, Dec 12, 2016 at 04:54:18PM +0200, Konstantin Belousov wrote:
> On Sun, Dec 11, 2016 at 11:47:09PM +0300, Slawa Olhovchenkov wrote:
> > Booting...
> > ESC[01;00H8+0x8+0xe9bdc]
> > KDB: debugger backends: ddb
> > KDB: current
On Sun, Dec 11, 2016 at 11:47:09PM +0300, Slawa Olhovchenkov wrote:
> Booting...
> ESC[01;00H8+0x8+0xe9bdc]
> KDB: debugger backends: ddb
> KDB: current backend: ddb
> exit from kdb_init
> KDB: enter: Boot flags requested debugger
>
On Mon, Dec 12, 2016 at 01:46:21AM +0300, Slawa Olhovchenkov wrote:
> > > > > > Can you show the verbose dmesg up to the failure point ?
> > > > > > In particular, the SMAP lines should be relevant.
> > > > >
> > > > > KDB: debugger backends: ddb
> > > > > KDB: current backend: ddb
> > > > >
On Mon, Dec 12, 2016 at 12:15:53AM +0300, Slawa Olhovchenkov wrote:
> On Sun, Dec 11, 2016 at 11:47:09PM +0300, Slawa Olhovchenkov wrote:
>
> > On Sun, Dec 11, 2016 at 10:06:54PM +0200, Konstantin Belousov wrote:
> >
> > > On Sun, Dec 11, 2016 at 10:45:59PM +0300, Slawa Olhovchenkov wrote:
> >
On Sun, Dec 11, 2016 at 11:47:09PM +0300, Slawa Olhovchenkov wrote:
> On Sun, Dec 11, 2016 at 10:06:54PM +0200, Konstantin Belousov wrote:
>
> > On Sun, Dec 11, 2016 at 10:45:59PM +0300, Slawa Olhovchenkov wrote:
> > > On Sun, Dec 11, 2016 at 09:26:56PM +0200, Konstantin Belousov wrote:
> > >
>
On Sun, Dec 11, 2016 at 10:06:54PM +0200, Konstantin Belousov wrote:
> On Sun, Dec 11, 2016 at 10:45:59PM +0300, Slawa Olhovchenkov wrote:
> > On Sun, Dec 11, 2016 at 09:26:56PM +0200, Konstantin Belousov wrote:
> >
> > > On Sun, Dec 11, 2016 at 10:16:26PM +0300, Slawa Olhovchenkov wrote:
> > >
On Sun, Dec 11, 2016 at 10:45:59PM +0300, Slawa Olhovchenkov wrote:
> On Sun, Dec 11, 2016 at 09:26:56PM +0200, Konstantin Belousov wrote:
>
> > On Sun, Dec 11, 2016 at 10:16:26PM +0300, Slawa Olhovchenkov wrote:
> > > On Sun, Dec 11, 2016 at 09:21:11PM +0300, Slawa Olhovchenkov wrote:
> > >
> >
On Sun, Dec 11, 2016 at 09:26:56PM +0200, Konstantin Belousov wrote:
> On Sun, Dec 11, 2016 at 10:16:26PM +0300, Slawa Olhovchenkov wrote:
> > On Sun, Dec 11, 2016 at 09:21:11PM +0300, Slawa Olhovchenkov wrote:
> >
> > > On Sat, Nov 26, 2016 at 05:57:47PM +0200, Konstantin Belousov wrote:
> > >
On Sun, Dec 11, 2016 at 10:16:26PM +0300, Slawa Olhovchenkov wrote:
> On Sun, Dec 11, 2016 at 09:21:11PM +0300, Slawa Olhovchenkov wrote:
>
> > On Sat, Nov 26, 2016 at 05:57:47PM +0200, Konstantin Belousov wrote:
> >
> > > On Sat, Nov 26, 2016 at 12:21:24PM +0300, Slawa Olhovchenkov wrote:
> > >
On Sun, Dec 11, 2016 at 09:21:11PM +0300, Slawa Olhovchenkov wrote:
> On Sat, Nov 26, 2016 at 05:57:47PM +0200, Konstantin Belousov wrote:
>
> > On Sat, Nov 26, 2016 at 12:21:24PM +0300, Slawa Olhovchenkov wrote:
> > > I am try to enable NUMA in bios and can't boot FreeBSD.
> > > Boot stoped
On Sat, Nov 26, 2016 at 05:57:47PM +0200, Konstantin Belousov wrote:
> On Sat, Nov 26, 2016 at 12:21:24PM +0300, Slawa Olhovchenkov wrote:
> > I am try to enable NUMA in bios and can't boot FreeBSD.
> > Boot stoped after next messages:
> >
> > ===
> > Booting...
> > KDB: debugger backends: ddb
>
On 26 November 2016 at 13:59, Slawa Olhovchenkov wrote:
> On Sat, Nov 26, 2016 at 01:55:14PM -0800, Adrian Chadd wrote:
>
>> ok, hm. then i don' know offhand, not without putting in printf debugging. :)
>
> I am not expert in this code, I am need you patches for printf debugging.
On Sat, Nov 26, 2016 at 01:55:14PM -0800, Adrian Chadd wrote:
> ok, hm. then i don' know offhand, not without putting in printf debugging. :)
I am not expert in this code, I am need you patches for printf debugging.
> On 26 November 2016 at 13:51, Slawa Olhovchenkov wrote:
> >
ok, hm. then i don' know offhand, not without putting in printf debugging. :)
-a
On 26 November 2016 at 13:51, Slawa Olhovchenkov wrote:
> On Sat, Nov 26, 2016 at 01:49:00PM -0800, Adrian Chadd wrote:
>
>> Ok. So boot verbose and let's see what it says.
>
> See first message:
On Sat, Nov 26, 2016 at 01:49:00PM -0800, Adrian Chadd wrote:
> Ok. So boot verbose and let's see what it says.
See first message: it's already verbose boot.
Yes, only 3 lines.
>
> On 26 November 2016 at 10:39, Slawa Olhovchenkov wrote:
> > On Sat, Nov 26, 2016 at 09:44:49AM
Ok. So boot verbose and let's see what it says.
-adrian
On 26 November 2016 at 10:39, Slawa Olhovchenkov wrote:
> On Sat, Nov 26, 2016 at 09:44:49AM -0800, Adrian Chadd wrote:
>
>> The ACPI SRAT parsing code - sys/x86/acpica/srat.c .
>>
>> I'd start by enabling bootverbose -
On Sat, Nov 26, 2016 at 09:44:49AM -0800, Adrian Chadd wrote:
> The ACPI SRAT parsing code - sys/x86/acpica/srat.c .
>
> I'd start by enabling bootverbose - adds one echo (SLIT.Localities and
> the table); adds CPU affinity info (legacy, XAPIC, ACPI) and other
> locality stuff.
I am use r308809
The ACPI SRAT parsing code - sys/x86/acpica/srat.c .
I'd start by enabling bootverbose - adds one echo (SLIT.Localities and
the table); adds CPU affinity info (legacy, XAPIC, ACPI) and other
locality stuff.
-adrian
On 26 November 2016 at 09:37, Slawa Olhovchenkov wrote:
> On
On Sat, Nov 26, 2016 at 09:35:08AM -0800, Adrian Chadd wrote:
> It may be something to do with memory topology parsing. Maybe we need
> some more debugging there to try and catch it.
What debug you need?
> On 26 November 2016 at 01:21, Slawa Olhovchenkov wrote:
> > I am try to
It may be something to do with memory topology parsing. Maybe we need
some more debugging there to try and catch it.
-a
On 26 November 2016 at 01:21, Slawa Olhovchenkov wrote:
> I am try to enable NUMA in bios and can't boot FreeBSD.
> Boot stoped after next messages:
>
>
On Sat, Nov 26, 2016 at 07:07:20PM +0300, Slawa Olhovchenkov wrote:
> On Sat, Nov 26, 2016 at 05:57:47PM +0200, Konstantin Belousov wrote:
>
> > On Sat, Nov 26, 2016 at 12:21:24PM +0300, Slawa Olhovchenkov wrote:
> > > I am try to enable NUMA in bios and can't boot FreeBSD.
> > > Boot stoped
On Sat, Nov 26, 2016 at 05:57:47PM +0200, Konstantin Belousov wrote:
> On Sat, Nov 26, 2016 at 12:21:24PM +0300, Slawa Olhovchenkov wrote:
> > I am try to enable NUMA in bios and can't boot FreeBSD.
> > Boot stoped after next messages:
> >
> > ===
> > Booting...
> > KDB: debugger backends: ddb
>
On Sat, Nov 26, 2016 at 05:57:47PM +0200, Konstantin Belousov wrote:
> On Sat, Nov 26, 2016 at 12:21:24PM +0300, Slawa Olhovchenkov wrote:
> > I am try to enable NUMA in bios and can't boot FreeBSD.
> > Boot stoped after next messages:
> >
> > ===
> > Booting...
> > KDB: debugger backends: ddb
>
On Sat, Nov 26, 2016 at 12:21:24PM +0300, Slawa Olhovchenkov wrote:
> I am try to enable NUMA in bios and can't boot FreeBSD.
> Boot stoped after next messages:
>
> ===
> Booting...
> KDB: debugger backends: ddb
> KDB: current backend: ddb
So at least the hammer_time() has a chance to initialize
73 matches
Mail list logo