Upgrade from 2.2 RC to 2.2 Final… Kernel trap error 12 on boot
-
I have been running 2.2 for several months and was running an RC snapshot from Early January without issue. I upgraded to the final version today and on reboot I get a Trap error. This is on an Axiomtek i386 embedded device using hard drive and the full install (not the embedded install).
atapci0: <intel ich4="" udma100="" controller="">port 0x1f0-0x… <cut>ata0: <ata channel="">at channel 0 on atapci0
ata1: <ata channel="">at channel 1 on atapci0
cpu0 on motherboard
p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
pmtimer0 on isa0
gpioapu0: Environment returned (null)Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
faul virtual address = 0x0
faul code = supervisor read, page not present
instructino pointer = 0x20:0xc0da8cf0
stack pointer = 0x20:0xc2420c28
frame pointer = 0x20:0xc2420c34
code segment = base 0x0, limit 0xffffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 0 (swapper)
[ thread pid 0 tid 100000 ]
Stopped at strncmp+0x20: movzbl 0(%esi),%ebx
db>Anyone experience this?</cpu></ata></ata></cut></intel>
-
I removed the comment that the system was locked up because the USB keyboard wasn't working. It was a cable problem. It still crashes of course but the keyboard works at the db> prompt.
I just reinstalled the official RC build from early december and restored my config. I am back up and running. I will end up trying at some point if I can even boot the 2.2 Final installer instead of doing an upgrade to test it.
-
Not enough info there to tell. Next time you try, capture that screen along with the output of "bt" at that prompt.
-
Do you have the CF in there even if you're not using it?
I suggest you try this:
https://forum.pfsense.org/index.php?topic=20095.msg480824#msg480824A couple of firebox users have been hit with that exact issue even though it shouldn't be a problem running from a HD. Specifically you might read this: https://forum.pfsense.org/index.php?topic=85930.msg479775#msg479775
Steve
-
I tried the PIO4 and mount setting and they didn't make a difference.
The system does not have CF and only has a hard drive on the inboard ata controller. That is how it was during the upgrade too. No memory stick or anything plugged in.
I just wrote the memstick image to a USB hard disk and tried that. It fails with the same error when it boots before getting to the install menu. The boot options mentioned above don't change anything.
I am using the full install via console i386 version on an Axiomtek NA-0043A which is getting pretty old but it has been a great small embedded device for firewalls up until 2.2 final.
Edit: I forgot to mention that the USB keyboard does get locked up at the db prompt even after fixing the bad cable I was using so I can't run the bt command.
-
The fact the last thing that it shows is gpioapu, and that it changed between such a short period and one other person reported same, makes me pretty sure something in gpioapu caused that to break on hardware that returns unusually for smbios.system.product.
https://redmine.pfsense.org/issues/4363
Hopefully get that addressed for 2.2.1. -
Same issue with my FWA7204.
As a workaround, is there a way to disable GPIOAPU with a kernel option at boot?
Any other idea for a workaround?
If not, 2.2 is not an option for me until this problem is resolved. Right now it look I have to go back to 2.1.5.
Bummer! :'(
-
A workaround on the firebox was to enable ACPI in the BIOS. You might be able to do that.
https://forum.pfsense.org/index.php?topic=87542.msg484384#msg484384Steve
-
Try this at a loader prompt:
set hint.gpioapu.0.disabled=1And then add it to /boot/loader.conf.local
hint.gpioapu.0.disabled=1 -
A workaround on the firebox was to enable ACPI in the BIOS. You might be able to do that.
https://forum.pfsense.org/index.php?topic=87542.msg484384#msg484384Steve
Thanks for the tip, but no ACPI configuration available in BIOS configuration.
-
Try this at a loader prompt:
set hint.gpioapu.0.disabled=1And then add it to /boot/loader.conf.local
hint.gpioapu.0.disabled=1I gave it a try, but no effect.
Thank you.
-
Did it appear to actually disable the gpioapu driver? It no longer appears in the boot messages? Can you post a copy of that?
Did you at any time see a message relating to 'smbios.system.product' ?
Just to confirm this is your box: http://ibt.ca/v2/items/fwa7204/index.html
Steve
-
I missed the notifications on this thread.
I will try the 'set hint.gpioapu.0.disabled=1' tonight on my Axiomtek server and see if it allows it to work on my system.
If it doesn't work I will try to figure out how to get a snapshot full install (assuming that is an option) to test that has the latest fix that was mentioned in the redmine issue.
https://redmine.pfsense.org/issues/4363
" Updated by Ermal Luçi 6 days ago
Status changed from New to Feedback
gpioapu corrected to avoid comparison with NULL in strncmp." -
If it doesn't try this:
https://forum.pfsense.org/index.php?topic=88363.msg487877#msg487877Steve
-
This didn't help…
set hint.gpioapu.0.disabled=1The setting below did. I was able to boot the 2.2 i386 full install final CD.
set smbios.system.product="XPS"I assume if I put that in the 2.1.5 /boot/loader.conf.local file it will stay in the transition on the upgrade to the 2.2.
Thanks for the info.
-
Doesn't have to be XPS by the way just something other than APU or null.
Steve
-
Did it appear to actually disable the gpioapu driver? It no longer appears in the boot messages? Can you post a copy of that?
Did you at any time see a message relating to 'smbios.system.product' ?
Just to confirm this is your box: http://ibt.ca/v2/items/fwa7204/index.html
Steve
Hi, sorry for the delay, but i had other priorities.
There are no references to "smbios.system.product" in my boot log.
yes http://ibt.ca/v2/items/fwa7204/index.html is my box.
Now for the good news, I tried
set smbios.system.product="XPS"
And it looked like it does the trick. I was able to do a complete boot on the upgraded version installed on my box.
This is a good workaround for that problem. According to this post:
https://redmine.pfsense.org/issues/4363
a real solution should be available in version 2.2.1.
Thanks you again for the replies and for the good work.
-
Great, thanks for confirming that. :)
Should be fixed in 2.2.1 as you say.Steve
-
The only behavior that should be changed by that action is whether or not the reset button utility is run.
Try running /usr/local/sbin/APUresetbtn to see if that triggers the panic.
If you're brave. :-)
-
There are 2.2.1 snapshots available now, if someone with an affected system can test and report back here in this thread or on its bug ticket:
https://redmine.pfsense.org/issues/4363I'd like to confirm that's definitely good. It should be fixed, but we don't have any affected systems internally to fully verify.
