if you encountered in dmesg output entry such as:
CPU0: local APIC error 0x2
add this to /boot/device.hints
hint.apic.0.disabled="1"
the problem should disappear
if you encountered in dmesg output entry such as:
CPU0: local APIC error 0x2
add this to /boot/device.hints
hint.apic.0.disabled="1"
the problem should disappear
if you occured server panic on FreeBSD 9.2 using journaled soft updates you probably had not clean shutdown and there is some inconsistency (though filesystem is clean) – for better stability disable journaled soft updates:
boot into single mode and after full fsck do:
# tunefs -j disable /dev/filesystem # reboot
or if you want to using journaled soft updates do manual fsck in single user mode without using journal
# USE JOURNAL? [yn] n
then the server panics should not appear to the next unclean shutdown…
if you obtain:
ping: socket: Operation not permitted
although:
security.jail.allow_raw_sockets=1
is set in /etc/sysctl.conf
you should add an option in the rc.conf
jail_yourjailname_parameters="allow.raw_sockets=1"
or add this option in /etc/jail.conf if you are using new configuration scheme added in FreeBSD 9.1 – see man jail.conf