Is that a bug?
-
I'm trying the 2.0 now that it is a beta. When I booted the nanobsd version pfSense-2.0-BETA1-1g-20100212-2232-nanobsd from CF I get this shortly after boot. Any ideas what is wrong? 1.2.3 was working fine in this box for a long time.
…
kernel trap 12 with interrupts disabledFatal trap 12: page fault while in kernel mode
fault virtual address = 0xf000e2c3
fault code = supervisor read, page not present
instruction poRoot mount waiting for: usbus2 usbus1 usbus0
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
inter = 0x20:0xc0509799
stack pointer = 0x28:0xc2f71c9c
frame pointer = 0x28:0xc2f71cc0
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = 10 (idle) -
You have probably found a bug.
I suggest that next time this happens (or now if the system is still at the db> prompt) you type "bt" (the debugger's backtrace command) and post the output here along with the precise name of the corresponding install file (it might be different next time you see the problem). This information may be useful to someone with kernel debugging experience to help them figure out what went wrong. It may also be helpful to note if this happens reliably or intermittently.
-
If I set "ACPI Aware OS"="No" in BIOS this doesn't happend. When ACPI Aware OS is Yes then this is consistent and happens always. The only difference between each message is inter value, as well as MSW of stack and code pointers. The exact image that I used for the CF is pfSense-2.0-BETA1-1g-20100204-1241-nanobsd.img
Here is the output after bt:
db> bt
Tracing pid 10 tid 64003 td 0xc3036b90
acpi_battery_get_battinfo(c2e71cd4,c0abc632,1,c2e71cf4,c086174f,…) at acpi_battery_get_battinfo+0x2859
set_fpregs(1,c2e71cf4,c086174f,1,0,...) at set_fpregs+0x11b
cpu_idle(1,0,c3036b90,c2e71cf4,0,...) at cpu_idle+0x12
sched_idletd(0,c2e71d38,0,0,0,...) at sched_idletd+0x6f
fork_exit(c08616e0,0,c2e71d38) at fork_exit+0x90
fork_trampoline() at fork_trampoline+0x8
--- trap 0, eip = 0, esp = 0xc2e71d70, ebp = 0 ---
db> -
What type of hardware is this?
I've had a couple boxes that didn't work quite right with FreeBSD 8 and ACPI. It shouldn't hurt to disable it in the BIOS.
Unfortunately, if you've hit a bug here is would most likely be a FreeBSD bug and not a pfSense bug.
-
It is Norco-7732 motherboard based box which is designed for network appliances (http://www.norcotek.com/NORCO-7732V.php)
It is OK for now. All network ports and the wlan card work just fine with ACPI disabled.
-
I submitted this as FreeBSD problem report i386/144045.
Thanks,
Darin Peshev
