2.2 upgrade issue on a Watchguard XCS570
Just posting this in the hopes that it helps someone else avoid having their network down all day after an un-tested upgrade to 2.2. (By untested I mean me not testing the upgrade before hand)
I run a few WG XCS570's which have dual Intel Pro/1000 onboard nics as well as an intel 1gb pci card. After the upgrade the system failed to boot completely. It would simply get stuck on boot loading network devices. Disabling all devices allows the system to boot, or simply removing the add-in network adapter altogether.
During troubleshooting I reset the bios which led to the error 19 message:
Mount from ufs:/dev/ad0s1a failed with error 19.
Simply changing the HDD mode back to SATA resolved that. First hint was booting from the live disk it couldnt find the drive to recover config.xml or install fresh, although half the boot does execute successfully…
Anyways, after getting 2.2 to boot again, I was then unable to ever get both onboard interfaces to load. These happened to be lan and wan for me so I needed them both. Adding a different pci network card didnt help either. I was simply stuck at one interface.
Looking in dmesg I noticed the following: (something very similar to this, thanks to topper727 for posting this in the BSD forums) https://forums.freebsd.org/threads/nic-em-problem-on-freebsd-10.49677/
em0: <intel(r) 1000="" pro="" network="" connection="" 7.4.2="">port 0x4000-0x401f irq 16 at device 0.0 on pci2
pcib0: allocated type 3 (0xd0200000-0xd02fffff) for rid 20 of pcib2
pcib2: allocated initial memory window of 0xd0200000-0xd02fffff
pcib2: allocated memory range (0xd0200000-0xd021ffff) for rid 10 of em0
em0: Lazy allocation of 0x20000 bytes rid 0x10 type 3 at 0xd0200000
em0: attempting to allocate 1 MSI vectors (1 supported)
msi: routing MSI IRQ 256 to local APIC 0 vector 51
em0: using IRQ 256 for MSI
em0: Using an MSI interrupt
em0: Setup of Shared code failed
device_attach: em0 attach returned 6
Basically in my case I could see both Pro/1000 cards appear with different posts listed, something like:
port 0x4000-0x401f irq 16 at device 0.0 on pci2
port 0x5000-0x401f irq 14 at device 0.0 on pci3
and both were followed by em0 lines.
In the end, as Mark mentioned here:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196501
"hint.agp.0.disabled=1 in my loader.conf has resolved the problem."
Adding this in, rebooting, magically I had both interfaces back. The lan interface had lost its IP at some point in the process so I needed to re-assign it, but other than that things appear to be working once again.
Hopefully this helps someone else who might encounter something similar.</intel(r)>