pfSense

I can confirm this issue on a Gigabyte GA-J1900N-D3V. I've tried AMD64/i386 builds of 2.1.3 as well as 2.2-DEVELOPMENT-4g-amd64-nanobsd-vga-20140526-1016. No BIOS options have any impact.. just can't get it to boot :-(

Ken Masterson wrote:

Asrock Q1900M motherboard with Bay Trail Intel J1900 is unable to boot pfSense 2.1.3 live CD and USB images. A kernel panic is reported, with message "Bogus interrupt trigger mode".

pfSense 2.2-DEVELOPMENT snapshot 20140523-0808 is also affected.

FreeNAS bug #4996 appears to be the same problem, and links to freeBSD ticket 187966, which includes a patch.

Dan E wrote:

I can confirm this issue on a Gigabyte GA-J1900N-D3V. I've tried AMD64/i386 builds of 2.1.3 as well as 2.2-DEVELOPMENT-4g-amd64-nanobsd-vga-20140526-1016. No BIOS options have any impact.. just can't get it to boot :-(

Ken Masterson wrote:

Asrock Q1900M motherboard with Bay Trail Intel J1900 is unable to boot pfSense 2.1.3 live CD and USB images. A kernel panic is reported, with message "Bogus interrupt trigger mode".

pfSense 2.2-DEVELOPMENT snapshot 20140523-0808 is also affected.

FreeNAS bug #4996 appears to be the same problem, and links to freeBSD ticket 187966, which includes a patch.

I can confirm on Gigabyte GA-J1900N-D3V as well.

I can confirm the same issue with ASUS J1900I-C. Both with pfsense 2.1.3 and with pfSense-memstick-serial-2.2-DEVELOPMENT-amd64-20140613-1600.img.

So this looks like a BIOS bug (bad ACPI table) that would be possible to workaround.
Those of you with the Gigabyte GA-J1900N-D3V have you updated to the most recent BIOS (F3)? There are other running that board successfully:
https://forum.pfsense.org/index.php?topic=73518.msg418094#msg418094

Steve

I'm having no luck getting pfsense to boot on my Intel NUC DN2820. Kernel panics with "Bogus interrupt trigger mode.".

Same problem here on the Gigabyte J1900N-D3V motherboard.
Also put some info up on this link on the forum:
https://forum.pfsense.org/index.php?topic=72305.15

Someone pointed out that this appears to be a BIOS ACPI table problem. I suggest that we start asking manufacturers if they can update their BIOS to resolve the issue.

I have logged a call with Gigabyte siting the BIOS ACPI issues and that F3 bios update does not address this problem.
Lets see how good Gigabyte is in addressing this issue.
Will post any updates back here as and when I get them.

Still no reply from Gigabyte...

I doubt you'll get a reply in any reasonable amount of time from motherboard manufacturers, but maybe if enough people make noise it'll get fixed in a future BIOS update.

This has been worked around in FreeBSD, though apparently not MFCed to 10-STABLE, so not in 2.2 at this time.

A response.... and the last gigabyte anything I ever buy!

"

Thank you for your kindly mail and inquiry. According to the specification on our product page, this motherboard only supports Windows 8.1/8 32-bit/64-bit and Windows 7 64-bit. Due to different Linux support condition provided by chipset vendors, please download Linux driver from chipset vendors' website or 3rd party website. If you have any problem with Linux, we suggest you to use the operation system the product can support. Thank you for your cooperation.

Regards,
GIGABYTE

"

Just for info, no change with release 2.1.4
As said above, the workaround did not make it into this release.

How do we get it in the next update?

I am not entirely sure...

Chris Buechler seemed to know a little about this, as stated above "This has been worked around in FreeBSD, though apparently not MFCed to 10-STABLE, so not in 2.2 at this time."

Chris, how do we make this happen?

Chris Buechler wrote:

this was since fixed in 9 and 10 stable FreeBSD, current 2.2 should work here

I can confirm that the issue appears to be fixed in the most recents builds of pfSense 2.2.x