https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220453
--- Comment #10 from p...@twisted.org.uk --- Just a quick one, will try and add more detail tomorrow. I am using r334458 on STABLE-11 which was more or less the point where 11_2 branched I believe. I can't see anything in 11_2 after that point which is mlx4en or linuxkbi related. I can try doing an update tomorrow to the latest STABLE and see though. Will try and prepare a box just for testing this. The compile has the following in src.conf # All our Intel machines are post-Core2 CPUTYPE?=core2 # We are using exim and cups WITHOUT_SENDMAIL=true WITHOUT_LPR=true and the following in make.conf # Build ports in local WRKDIRPREFIX=/usr/local/port-build # Use new format packages WITH_PKGNG=yes DISABLE_VULNERABILITIES=yes # If we install cups it overwrites the base CUPS_OVERWRITE_BASE=yes I switched the interface over to accelerated networking and rebooted, but it still came up using hn0. So I added a 'mlx4en_load="YES"' to loader.conf and rebooted - which gave me the panic. I tried many times, it panicked every time. The only oddity in the setup is I am booting off ZFS instead of UFS. Drive is GPT partitioned, and I have the following in loader.conf boot_serial="YES" comconsole_speed="115200" console="comconsole" vfs.mountroot.timeout="300" kern.geom.label.disk_ident.enable="0" kern.geom.label.gptid.enable="0" ahci_load="YES" aesni_load="YES" cryptodev_load="YES" zfs_load="YES" vfs.zfs.arc_max="1G" vfs.zfs.prefetch_disable="1" vfs.zfs.txg.timeout="5" vfs.zfs.vdev.cache.size="10M" vfs.zfs.vdev.cache.max="10M" Don't know if any of that is significant at all - I assume adding the line to loader.conf is the right thing to do, yes ? -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"