So, another datapoint on this - I just PXE booted the 12.0-RELEASE image
downloaded from https://mfsbsd.vx.sk/ and that works fine. Which means
that it siether something which has crept in since 12.0-RELEASE or its
something to do with my config on that machine.
I did try and buld an mfsroot
On 06/02/2019 12:16, Andrey V. Elsukov wrote:
Hi,
this doesn't look very useful.
Do you have some specificity with this host except carp? Some
modifications to kernel config, lagg, jails, etc.
No, none of those. Its a supermicro motherboard, runs FreeBSD
GENERIC and mysql+redis on top,
On 05.02.2019 18:06, Pete French wrote:
> The branch and revision is 12.0-STABLE r343538 GENERIC
>
>> # kgdb
>>
>> (kgdb) list *ether_output+0x6b6
>
> trying to do this on the actual box is hard, as it panics, but on another
> machine running the same build I get this, which should suffice if
> Hi,
>
> What branch and revision do you use? Can you install gdb and then obtain
> this information:
The branch and revision is 12.0-STABLE r343538 GENERIC
> # kgdb
>
> (kgdb) list *ether_output+0x6b6
trying to do this on the actual box is hard, as it panics, but on another
machine running
On 17.01.2019 15:19, Pete French wrote:
> so, having got a workaround for yesterdays problems, I now went to upgrade my
> other pair of boxes using CARP. No 'pf' on these, just one shared address.
> This is the setup I have tested in development and it works fine.
>
> I install the new kenel and
Just to get the subject correct, as I tested this disabling CARP and I
still see the panic when going multi-user. It netwprking related as the
panic is in the ARP code, and seems to happen when the network
interfaces are configured. The machine was using a mix of em and igb
interfaces, but
> > To point out the obvious, booting a 12.0 kernel with 11.0 userland to
> > multiuser mode is seriously unsupported. You really need to boot to
> > single user and install 12.0 userland to really expect things to work.
>
> Yes, good point. This has worked on every other machine I have upgraded
To point out the obvious, booting a 12.0 kernel with 11 userland to
multiuser mode is seriously unsupported. You really need to boot to
single user and install 12.0 userland to really expect things to work.
Yes, good point. This has worked on every other machine I have upgraded
from 11 to
On Thu, Jan 17, 2019 at 4:21 AM Pete French
wrote:
> so, having got a workaround for yesterdays problems, I now went to upgrade
> my
> other pair of boxes using CARP. No 'pf' on these, just one shared address.
> This is the setup I have tested in development and it works fine.
>
> I install the
so, having got a workaround for yesterdays problems, I now went to upgrade my
other pair of boxes using CARP. No 'pf' on these, just one shared address.
This is the setup I have tested in development and it works fine.
I install the new kenel and do the first reboot - and I get the panic
below.
10 matches
Mail list logo
