Hi Michael,

        Do you think you can provide us with a stack trace, at the least?
  This would deffinately give us something more to work with.
  Unfortunately, with this information, it's very difficult to pin-point
  the problem, as we're not certain as to what is at 0xc029e6cb, exactly.
        Also, is there anything particular that you notice that is happening
  in parallel to this? Anything special you're doing?

On 3 Oct 2000, Michael Harnois wrote:

> The past three days or so with -current my system has been locking up
> solid under load. Today I was fortunate enough to have in happen when
> in console mode so that I could see the problem:
> Fatal trap 12: page fault while in kernel mode
> fault virtual address           = 0x10000
> fault code                      = supervisor read, page not present
> instruction pointer             = 0x8:0xc029e6cb
> stack pointer                   = 0x10:0xcefdfe18
> frame pointer                   = 0x10:0xccfdfe20
> code segment                    = base 0x0, limit 0xffff, type 0x1b
>                                 = DPL 0, pres 1, def32 1, gran 1
> processor eflags                = interrupt enabled, resume, IOPL = 0
> current process                 = 2355 (procmail)
> trap number                     = 12
> panic: page fault
> acpi0: acpi_io_pml_enable(1) = (0)
> acpi0: acpi_io_gpe0_enable(1) = (0)
> syncing disks...
> -- 
> Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA 
> [EMAIL PROTECTED]                      [EMAIL PROTECTED] 
>  No man knows how bad he is 
>  till he has tried very hard to be good. -- C.S. Lewis

  Bosko Milekic

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

Reply via email to