PLEASE read this:

        Basically, by just looking at the page fault message, this appears to
  be the dereferencing of a NULL pointer. That's all that I'm afraid pretty
  much anybody will be able to conclude from this unless you, at least,
  provide us with a backtrace as well as an assembly dump of whatever
  function the crash occured in.

On Tue, 22 Aug 2000, Patrick Gardella wrote:

> I've been working for a while to try to figure out a problem I'm having
> here.
> I did a buildworld Sunday, and started to get kernel panics on boot when
> it probed fxp.  So I removed fxp from my kernel and loaded it as a
> module (via loader.conf.local).  It paniced.  Then I unloaded the
> if_fxp.ko on startup, and it booted.  But if I load the fxp module now,
> after a full boot, everything is great.  Rebooting with fxp in the
> kernel or loading the module on boot will cause a panic *every* time.
> Thinking it might be build problem, I redid the build/install/kernel
> again on Monday, and am having the same problems.  The panics only
> started on the upgrade from a -current dated sometime in early July.
> As you will see from below, this is an SMP machine (dual P200) with 256
> Megs RAM.
> I am also using NETGRAPH to run PPPoE.
> Any ideas?
> Patrick
> The panic is:
> Fatal trap 12: page fault while in kernel mode
> mp_lock=00000005; cpuid = 0;
> fault virtual address   = 0x0
> fault code      = supervisor read, page not present
> instruction pointer = 0x8:0xc034e304
> stack pointer       = 0x10:0xc038bea8
> frame pointer       = 0x10=0xc038bebc
> code segment        = base 0x0, limit 0xfffff, type 0x1b
>             = DPC 0, pres 1, def 32 1, gran 1
> processor eflag     = interrupt enabled, resume, IOPC=0
> current process     = 0 (swapper)
> interrupt mask      = net tty bio cam <- SMP:XXX
> trap number         = 12
> panic: page fault


 Bosko Milekic  *  Voice/Mobile: 514.865.7738  *  Pager: 514.921.0237

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

Reply via email to