Fw reboots 1.2.3
-
this is from dmesg, what can you guys get out of that?
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x10
fault code = supervisor write, page not present
instruction pointer = 0x20:0xc0be6f24
stack pointer = 0x28:0xd646cba8
frame pointer = 0x28:0xd646cbbc
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 57413 (php)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 3d22h19m50s
Cannot dump. No dump device defined.
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting…/F
-
Not sure, but pfSense 1.2.3-RC1 officially came out last night, so you may want to upgrade to that version and see if the problem persists.
-
Hi! I just installed pfsense 1.2.3RC1 and with a usb dongle cnet cwd-854 with rt73 (rt2573) chip, and when using wifi (as access point) i get the same problem after a while.
One thing I think should be checked is that my cellphone n95 heats up a lot when connected to pfsense, but when connected to a linksys at the same distance it doesn't heat.
Also when I check properties of the wireless connection in the n95 i found that "Mode" and "Security" are empty, while when I use the other network i get "Infrastructure" in mode and wpa/wpa2 in security.
And when connecting with my laptop I get frequent, 2 times per second, change on the wpa key.
-
It's highly unlikely the two are related at all, aside from the fact that they're both kernel panics. The cause is hardware-specific FreeBSD problems, which we can't do anything about (and the brief panic message is of no use to determine the cause).
You may want to try one of the FreeBSD 7.2-based 1.2.3 snapshots to see if that changes anything.
http://snapshots.pfsense.org/FreeBSD_RELENG_7_2/pfSense_RELENG_1_2/?C=M;O=DSee also:
http://doc.pfsense.org/index.php/Policy_on_FreeBSD_issues
-
I think is something with corrupted IRQs…. and with USB. Do you know if there is a way to not use IRQs for USB devices?
-
or maybe assign manually IRQ for vr0 and vr1? because i found that USB and the NICs are getting the same IRQ and that ALWAYS the failure is with vr0 and ehci that share the same IRQ….
I found that it is an old issue with freebsd with realtek NICs.
-
i just upgraded to latest version based on 7.2, and is the same….. i think that i need to change the irq for ehci, do you know how can I do that?
I found that with a tool called pciconf some sort of things like this can be done, but i can't find a well documented manual for this task.
-
A BIOS upgrade may solve what you're seeing. Also try resetting your BIOS to defaults, might be something weird in there that messes things up. And if that fails, then try messing with relevant BIOS settings.
-
I just tested in another machine with other type of hardware… it seems to be a problem with usb driver, because in this machine the irq isn't shared and it fails the same way, but the process that generates the panic is the uhci process....
-
I just tested in another machine with other type of hardware… it seems to be a problem with usb driver, because in this machine the irq isn't shared and it fails the same way, but the process that generates the panic is the uhci process....
The "current" process at the time of the crash is not necessarily the process generating the panic. The "current" process at the time of the panic may just have the poor luck of being the process that was suspended at the time the kernel had to do something else.
The drivers for wireless USB devices interact with the driver(s) for the USB hardware and with the network protocol stack. More information is needed to identify the cause of the panic. Perhaps you might be able to get access to a debug kernel which will print out a stack trace on panic.
Which driver is used for your usb stick: rum or ural?
-
It is rum…
and is always the same process, i tested this about 15-20 times and always is the same process.
