Infrequent boot failure with 11.1

2017-08-09 Thread Rajil Saraswat
Hello, I have a Supermicro X10Dri-T motherboard which refuses to boot 50% of the time. It hangs with the message DMAR: Found table at 0x7995ccb0 x2APIC should be disabled by DMAR table but already enabled by BIOS; enabling. Event timer "LAPIC" quality 600 ACPI APIC Table: Package ID shift: 5

Re: SLAAC not working

2017-08-09 Thread Greg Rivers
On Wednesday, August 09, 2017 17:41:47 Hiroki Sato wrote: > Greg Rivers wrote > in <2045487.fzlpjxt...@flake.tharned.org>: > > gc> > 2. What is shown by the command "ping6 ff02::1%lagg0" ...? > gc> > > gc> $ ping6 -c 2 ff02::1%lagg0 > gc> PING6(56=40+8+8 bytes)

Re: Is it worth waiting for AMD Opteron X3000 support in FreeBSD? Bug [221350]

2017-08-09 Thread Rafal Lukawiecki
Following suggestion by Miroslav Lachman I have tested a few other releases of FreeBSD to see if this issue still persists, and if it was perhaps a regression. Unfortunately, in all the tests, 9.3-12.0-CURRENT, I get exactly the same error. The initial boot stops after displaying messages about

Re: Is it worth waiting for AMD Opteron X3000 support in FreeBSD? Bug [221350]

2017-08-09 Thread Rafal Lukawiecki
Many thanks, Kurt, for pointing out those other 3 bug reports. On the face of it, they look different to mine. In my case, and in the case of another user who has reported this on the FreeNAS forum (affecting FreeBSD 11.0), the boot progresses past the point shown in the 3 reports that you have

Re: Is it worth waiting for AMD Opteron X3000 support in FreeBSD? Bug [221350]

2017-08-09 Thread Miroslav Lachman
Rafal Lukawiecki wrote on 2017/08/09 14:47: Apologies if this is the wrong way to approach the FreeBSD community wisdom: I am new here, please forgive. I am unable to boot/install FreeBSD-11.1-RELEASE-amd64-memstick.img (dated 2017-July-21) on a brand-new HPE MicroServer Gen10 containing an

Re: Is it worth waiting for AMD Opteron X3000 support in FreeBSD? Bug [221350]

2017-08-09 Thread Kurt Jaeger
Hi! > The full details with boot console outputs: > https://forums.freebsd.org/threads/61936/ > > Bugzilla bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350 Please compare with https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213155

Is it worth waiting for AMD Opteron X3000 support in FreeBSD? Bug [221350]

2017-08-09 Thread Rafal Lukawiecki
Apologies if this is the wrong way to approach the FreeBSD community wisdom: I am new here, please forgive. I am unable to boot/install FreeBSD-11.1-RELEASE-amd64-memstick.img (dated 2017-July-21) on a brand-new HPE MicroServer Gen10 containing an AMD Opteron X3421. Boot hangs very early in

11.0: Fatal trap 12: page fault while in kernel mode

2017-08-09 Thread Anton Shterenlikht
http://eis.bris.ac.uk/~mexas/core.txt.9 vmcore.9 is >450MB: http://cmplx.uk/pic/vmcore.9 Thanks Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to

Re: SLAAC not working

2017-08-09 Thread Hiroki Sato
Greg Rivers wrote in <2045487.fzlpjxt...@flake.tharned.org>: gc> > 2. What is shown by the command "ping6 ff02::1%lagg0" and "rtsol -dD lagg0"? gc> > gc> $ ping6 -c 2 ff02::1%lagg0 gc> PING6(56=40+8+8 bytes) fe80::ae16:2dff:fe1e:b880%lagg0 --> ff02::1%lagg0

Re: SLAAC not working

2017-08-09 Thread Greg Rivers
On Wednesday, August 09, 2017 16:26:50 Hiroki Sato wrote: > The configuration looks correct to me, but two questions: > > 1. Does "sysctl net.inet6.ip6.forwarding" command show "0"? > $ sysctl net.inet6.ip6.forwarding net.inet6.ip6.forwarding: 0 > 2. What is shown by the command "ping6

Re: SLAAC not working

2017-08-09 Thread Hiroki Sato
Greg Rivers wrote in <1557648.bebeymq...@flake.tharned.org>: gc> On Monday, August 07, 2017 15:57:04 Andrey V. Elsukov wrote: gc> > So, set net.inet6.icmp6.nd6_debug=1 and show what you have in the gc> > ndp -p gc> > ndp -r gc> > ndp -i lagg0 gc> > gc> #

Re: SLAAC not working

2017-08-09 Thread Greg Rivers
On Monday, August 07, 2017 15:57:04 Andrey V. Elsukov wrote: > So, set net.inet6.icmp6.nd6_debug=1 and show what you have in the > ndp -p > ndp -r > ndp -i lagg0 > # sysctl net.inet6.icmp6.nd6_debug=1 net.inet6.icmp6.nd6_debug: 0 -> 1 # suspend [1] + Stopped (SIGSTOP)su - $ ndp -p