Retired > 2.0-RC Snapshot Feedback and Problems - RETIRED

pfSense crashed on Alix

<< < (8/10) > >>

Uxorious:
I just had what is possibly the same problem on an old Dell OptiPlex GX200 with a dual Intel gigabit card installed.

LAN IP was completely dead, and I did not have a keyboard so no backtrace:
em1: watchdog timeout -- resetting
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0xe0500a4
fault code = supervisor read, page not present
instruction pointer - 0x20:0xc0a63aa7
stack pointer = 0x28:0xe2c547c4
frame pointer = 0x28:0xe2c547f0
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 = 0 (em0 taskq)
[thread pid 0 tid 64027]
Stopped at rn_match+0x17: movl 0xc(%eax),%ebx

Build used was pfSense-2.0-BETA1-20100216-2021.iso installed to the HDD.
Box had been running for almost 2 days when it happened.

Uxorious:

--- Quote from: Uxorious on February 18, 2010, 10:29:22 pm ---Stopped at rn_match+0x17: movl 0xc(%eax),%ebx

--- End quote ---

It happened again some 20 hours later.
LAN dead again, but stopped at exactly the same instruction.
Since writing down the bactrace was too painful, I took a picture instead.

ttlinna:

--- Quote from: Uxorious on February 18, 2010, 10:29:22 pm ---I just had what is possibly the same problem on an old Dell OptiPlex GX200 with a dual Intel gigabit card installed.

LAN IP was completely dead, and I did not have a keyboard so no backtrace:
em1: watchdog timeout -- resetting
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0xe0500a4
fault code = supervisor read, page not present
instruction pointer - 0x20:0xc0a63aa7
stack pointer = 0x28:0xe2c547c4
frame pointer = 0x28:0xe2c547f0
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 = 0 (em0 taskq)
[thread pid 0 tid 64027]
Stopped at rn_match+0x17: movl 0xc(%eax),%ebx

Build used was pfSense-2.0-BETA1-20100216-2021.iso installed to the HDD.
Box had been running for almost 2 days when it happened.

--- End quote ---

I've had multiple similar problems. Unfortunately I haven't been able to grab the log since the problems have occured in production environments. Network just stops suddenly working. It can run well for days or just for an hour or so.

I've rolled back also to 1.2.3 and it's running fine on the same hardware. I've had problems both with Alix 2d3 boards and different pc hardware.

My config includes use of limiters. Is it possible that it causes problems?

That's just my hunch, since I've got older snapshots running fine without limiters.

BR,

Tommi

Uxorious:

--- Quote from: ttlinna on February 22, 2010, 02:07:00 am ---I've had multiple similar problems. Unfortunately I haven't been able to grab the log since the problems have occured in production environments. Network just stops suddenly working. It can run well for days or just for an hour or so.

My config includes use of limiters. Is it possible that it causes problems?
That's just my hunch, since I've got older snapshots running fine without limiters.

--- End quote ---

My config is fairly simple.
WAN and another WAN on OPT.
A couple NAT/FW rules inbound.
Nothing else.

xbipin:
my alix with 20th feb snapshot works perfect and older versions also have been running stable enough for me for as much as 15 days then its no crash but i usually endup trying newer snapshots.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version