Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Jul 2017 17:51:07 +0200
From:      Nicolas Embriz <nbari@tequila.io>
To:        Valentin Nechayev <netch@netch.kiev.ua>
Cc:        "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>
Subject:   Re: GEOM: ada0: the secondary GPT header is not in the last LBA or random: unblocking device. when using more than 2 cores
Message-ID:  <CAGuJ=Ck9d686Zk9OY3ZUB7id769Z=tMpk0o%2BC-GwX6vauXuFLA@mail.gmail.com>
In-Reply-To: <20170717091125.GA8450@netch.kiev.ua>
References:  <CAGuJ=CnBvEViR00j57Af78Sk7MuiEMyR_1A-ZNiBx7qFjCDmxQ@mail.gmail.com> <CANCZdfrGgEBdiiaDX9ND87h%2Bi4RB2FvD5dp2EMoO1nuKakfHPg@mail.gmail.com> <CAGuJ=CkwWey2FCa6zWmAJw-pvJQndZ8JRwHyg=n_-WwC2capww@mail.gmail.com> <CAGuJ=CkN5DYaObu4YTga=gZNdvo9j2ThfK9zq5pKtYBcZO6SiQ@mail.gmail.com> <CAGuJ=C=BwF6nz2aAQEmQVsEDHQEF9%2BiuKuWN42M65D57Kx5jqA@mail.gmail.com> <20170717091125.GA8450@netch.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I notice that in 11.1 there is this new option EARLY_AP_STARTUP, I add
it to the kernel and testing also with a GENERIC and seems to be working
(no panics when using more than 2 cores)

But wondering what exactly =E2=80=9CEARLY_AP_STARTUP=E2=80=9D does and why =
is that when
using one single core kernel and not using this option the kernel doesn't
panic but if using more than 2 cores it panics at boot time.

Regards.


On Mon, Jul 17, 2017 at 11:11 AM, Valentin Nechayev <netch@netch.kiev.ua>
wrote:
>
> hi,
>
>  Sun, Jul 16, 2017 at 12:16:14, nbari wrote about "Re: GEOM: ada0: the
secondary GPT header is not in the last LBA or random: unblocking device.
when using more than 2 cores":
>
> > Setting up harvesting:
> >
[UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,NET_ETHER,NET_TUN,MOUSE,KEYBOARD,ATTA=
CH,CACHED
> > Feeding entropy: .
> > spin lock 0xffffffff80db45c0 (smp rendezvous) held by 0xfffff8000437856=
0
>
> Are you using a custom kernel?
> I had experienced panics just with random device on transition
> 10.2 -> 10.3 by source, and they were solved by temporary disabling of
> rdrand_rng, despite following reenabling of this device settled normal
> working. (Regrettably, I haven't got the panic details.)
>
>
> -netch-



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGuJ=Ck9d686Zk9OY3ZUB7id769Z=tMpk0o%2BC-GwX6vauXuFLA>