APU2c0: USB install of 2.4.2-RELEASE fails with "Fatal trap 9: general protection fault while in kernel mode"



  • I have a pcengines APU2c0 model that is currently running 2.3.5-RELEASE on coreboot v4.8.0.7. I thought that if I updated the BIOS of apu, that I could then install v 2.4.x of pfsense, but I keep on running into the same installation error during a USB install:

    Fatal trap 9: general protection fault while in kernel mode
    cpuid = 3; apic id = 03
    instruction pointerxml o= 0x20:0xffffffff80b265abmmcsd0s1[WRITE(offset=3223552, length=4096)]error = 30
    stack pointermmc        = 0x28:0xfffffe008d728020h=4096)]error = 30
    frame pointermmc        = 0x28:0xfffffe008d728050h=4096)]error = 30
    code segmentg up on dirt= base 0x0, limit 0xfffff, type 0x1be VCHR
        usecount 1, writecou= DPL 0, pres 1, long 1, def32 0, gran 1008774e00
    processor eflagsTIVE)   = interrupt enabled, resume, IOPL = 0
    current processfffff8000= 1388 (dialog)ages 121 cleanbuf 120 dirtybuf 1
        lock type devfs: UNLOCKED
            dev mmcsd0s1
    diskid/DISK-014F948Fs1: g_vfs_done():diskid/DISK-014F948Fs1[WRITE(offset=3223552, length=4096)]error = 30
    g_vfs_done():diskid/DISK-014F948Fs1[WRITE(offset=3223552, length=4096)]error = 30
    g_vfs_done():diskid/DISK-014F948Fs1[WRITE(offset=3223552, length=4096)]error = 30
    fsync: giving up on dirty 0xfffff8002e7cc1d8: tag devfs, type VCHR
        usecount 1, writecount 0, refcount 123 mountedhere 0xfffff80010842000
        flags (VI_ACTIVE)
        v_object 0xfffff8001c4b91e0 ref 0 pages 121 cleanbuf 120 dirtybuf 1
        lock type devfs: UNLOCKED
            dev diskid/DISK-014F948Fs1
    [Could not locate an existing config.xml file!] Done.
    

    The stacktrace information appear slightly differently every failed install. I feels like FreeBSD 11 doesn't like some piece of hardware on my apu2c0.

    I have tried to install pfSense-CE-memstick-serial-2.4.2-RELEASE-amd64.img on these coreboot bios versions:

    • apu2_v4.0.15.rom
    • apu2_v4.0.22.rom
    • apu2_v4.6.0.rom
    • apu2_v4.6.10.rom
    • apu2_v4.8.0.7.rom

    main and legacy versions fail in the same way

    I have used dd and balenaEtcher on macOS to burn usb images of: pfSense-CE-memstick-serial-2.4.2-RELEASE-amd64.img and pfSense-CE-memstick-serial-2.3.5-RELEASE-amd64.img.

    I can install pfsense v2.3.5-RELEASE no problem, but any version of v2.4.x fails with that same "Fatal trap 9" error after the files have been extracted by the installer and tries to boot off the mSATA SSD disk.

    Here are the links I used to do the install:

    https://github.com/pcengines/apu2-documentation/blob/master/docs/pfSense-install-guide.md
    https://pcengines.ch/howto.htm#OS_installation

    Oh one other detail that may or may not be related:

    When I plug in the 2.4.2-RELEASE USB stick, I see these error messages on the console for the 2.3.5-RELEASE pfsense/FreeBSD10 OS:

    GEOM: da0: the secondary GPT header is not in the last LBA.
    GEOM: diskid/DISK-123456789ABC: the secondary GPT header is not in the last LBA.
    

    I'd like to know if this is related to the install failure error "Fatal trap9: general protection fault while in kernel mode"

    Does anyone know if I'm missing something obvious that would unblock my install of pfsense v2.4.x on my APU2c0 pcengines unit?



  • anyone?



  • Hi.

    Current release is 2.4.4-Release-p1, can you check this release?
    Running on a APU4b4 ootb (same cpu, nic, more ram) without problems.


  • Rebel Alliance Developer Netgate

    @bradford said in APU2c0: USB install of 2.4.2-RELEASE fails with "Fatal trap 9: general protection fault while in kernel mode":

    g_vfs_done():diskid/DISK-014F948Fs1[WRITE(offset=3223552, length=4096)]error = 30

    That implies that your disk is dead/dying. The error mentions mmsd0 which is the SD card, not mSATA. So if you have an SD card in there at the same time as the mSATA disk, remove it. The installer may have used the SD card instead of the mSATA.



  • @jimp This was the fix. I removed the SD card, and the installer worked fine. It does seem a bit bizarre because I did specify the SSD drive during the install wizard. The other weird detail is that the busted SD card did not prevent me from installing v2.3.5. Anyway, you win all the cookies.