Sudden crash

Mike Jakubik mikej at rogers.com
Wed Aug 4 08:20:15 PDT 2004


Kenneth Stailey said:

> --- Mike Jakubik <mikej at rogers.com> wrote:
>
>> Hi all,
>>
>> One of my AMD64 boxes decided to crash all of a sudden. It was running
>> fine for a couple of weeks however, maybe its a hardware problem. The
>> hardware is an Asus SK8. Regardless i thought i would post the details
>> that i salvaged from the daily security log.
>>
>> Thanks.
>>
>> ---
>> mail.xxx.com kernel log messages:
>> > pid 603 (dovecot-auth), uid 0: exited on signal 10 (core dumped)
>> > Sorry, need DDB option to print backtrace pid 15214 (dovecot-auth),
>> > uid 0: exited on signal 10 (core dumped) Sorry, need DDB option to
>> > print backtraceSorry, need DDB option to print backtraceSorry, need
>> > DDB option to print backtrace pid 15328 (dovecot-auth), uid 0: exited
>> > on signal 10 (core dumped) kernel trap 12 with interrupts disabled
>> >
>> >
>> > Fatal trap 12: page fault while in kernel mode
>> > fault virtual address	= 0x48
>> > fault code		= supervisor read, page not present
>> > instruction pointer	= 0x8:0xffffffff801e6b17
>> > stack pointer	        = 0x10:0xffffffff94c41ad0
>> > frame pointer	        = 0x10:0xffffff0012b10000
>> > code segment		= base 0x0, limit 0xfffff, type 0x1b
>> > 			= DPL 0, pres 1, long 1, def32 0, gran 1
>> > processor eflags	= resume, IOPL = 0
>> > current process		= 35 (swi8: clock)
>> > trap number		= 12
>> > panic: page fault
>> >
>> > syncing disks, buffers remaining... 3797 3797 Copyright (c) 1992-2004
>> The FreeBSD Project.
>> > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993,
>> 1994
>> > 	The Regents of the University of California. All rights reserved.
>> > FreeBSD 5.2-CURRENT #0: Thu Jun 24 11:55:40 EDT 2004
>> >     root at mail.xxx.com:/usr/obj/usr/src/sys/MAIL

-snip-

> http://www.freebsd.org/releases/5.3R/todo.html
>
> << Problems persist with crashes and hangs under heavy load, especially
> under
> SMP. The recent introduction of full-scale preemption exasperated the
> problem,
> though it has been mitigated by a recently committed hack. Speculation on
> the
> source of the problem seems to center around races in critical section and
> spinlock handling and nesting. This needs to be driven to root cause and
> fixed
> in order for 5.3 to be considered STABLE. >>

I belive that preemption was not commited yet in my version. Thats
'FreeBSD 5.2-CURRENT #0: Thu Jun 24 11:55:40 EDT 2004'.





More information about the freebsd-amd64 mailing list