On 2003-01-19 03:44, Me <[EMAIL PROTECTED]> wrote:
> hi, i have a serious problem on a freebsd 4.6 on an i386...
>
> any time i try to use the ipfw command - even for ipfw show - the
> machine crashes and reboots automatically...
>
> the messages log file registers this:
> /kernel: Fatal trap 12: page fault while in kernel mode
> Jan 18 19:34:09 host /kernel: fault virtual address = 0x0
> Jan 18 19:34:09 host /kernel: fault code = supervisor read, page not present
> Jan 18 19:34:09 host /kernel: instruction pointer = 0x8:0x0
> Jan 18 19:34:09 host /kernel: stack pointer = 0x10:0xd2ef5ea8
> Jan 18 19:34:09 host /kernel: frame pointer = 0x10:0xd2ef5ebc
> Jan 18 19:34:09 host /kernel: code segment = base 0x0, limit 0xfffff, type 0x1b
> Jan 18 19:34:09 host /kernel: = DPL 0, pres 1, def32 1, gran 1
> Jan 18 19:34:09 host /kernel: processor eflags = interrupt enabled, resume, IOPL = 0
> Jan 18 19:34:09 host /kernel: current process = 632 (ipfw)
> Jan 18 19:34:09 host /kernel: interrupt mask = none
> Jan 18 19:34:09 host /kernel: trap number = 12
> Jan 18 19:34:09 host /kernel: panic: page fault

Can you build a kernel that includes debugging information and read
the ``Kernel Debugging'' chapter of the FreeBSD Developer's Handbook?
After that, you should be able to get a crash dump from your kernel
and post the information here.

> i have linux background and used to ipchanes...  but i'm new to ipfw
> on freebsd.

That's ok.  The FreeBSD documentation for ipfw(8) will help :-)

> in the rc.conf file the ipfw type is unknown which means that when
> rc.firewall gets called there is no firewall rules set up...  i
> don't see how this will make the machine crash when i type:
> # ipfw -a show
>
> i'm thinking of recompiling the kernel but not sure if this will
> help....

Not just your kernel.  That's not the way it works on FreeBSD.
Please, when upgrading, read carefully the file /usr/src/UPDATING and
follow the instructions it contains.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Reply via email to