Date: Thu, 6 Mar 2003 14:55:31 -0500 From: "Lanny Baron" <lnb@freebsdsystems.com> To: "John Ekins" <john.ekins@brightview.com>, <freebsd-smp@freebsd.org> Subject: Re: Regular panic on SMP system Message-ID: <006101c2e41a$58238280$0200a8c0@noemie> References: <20030306194400.4fa939e3.john.ekins@brightview.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I like that.. 'regular' Send me mine with extra sugar :) What Server Board are you using? Lanny ----- Original Message ----- From: "John Ekins" <john.ekins@brightview.com> To: <freebsd-smp@freebsd.org> Sent: Thursday, March 06, 2003 2:44 PM Subject: Regular panic on SMP system > Gents/ladies(!), > > I'm running several SMP systems but am having regular problems with one of > them. I'm not sure if this is really a question for the SMP or the questions > list, but I'm trying here first. > > The machines are dual Xeon 2.4GHz .5MB cache with hyperthreading enabled. They > are less than 2 weeks old. They have identical kernels, which leads me to > believe this is a hardware problem with this particular machine but I'm not > too sure. I'm looking for some advice. I've taken the liberty of posting the > log when the machine crashes below. > > I thought that "Fatal trap 12: page fault while in kernel mode" referred to > below suggests that something has eaten up the stack. These machines run Exim > + named + anti virus software. I consider them lightly loaded. > > Does anyone have any suggestions, and if I should post this to questions I > apologise. > > Cheers, > John. > > > Mar 6 10:12:45 mx0 /kernel: Fatal trap 12: page fault while in kernel mode > Mar 6 10:12:45 mx0 /kernel: mp_lock = 03000002; cpuid = 3; lapic.id = > 03000000 Mar 6 10:12:45 mx0 /kernel: fault virtual address = 0x0 > Mar 6 10:12:45 mx0 /kernel: fault code = supervisor write, page not > present Mar 6 10:12:45 mx0 /kernel: instruction pointer = > 0x8:0xc01995ca > Mar 6 10:12:45 mx0 /kernel: stack pointer = 0x10:0xe4bdbecc > Mar 6 10:12:45 mx0 /kernel: frame pointer = 0x10:0xe4bdbed0 > Mar 6 10:12:45 mx0 /kernel: code segment = base > 0x0, limit 0xfffff, type 0x1b > Mar 6 10:12:45 mx0 /kernel: = DPL 0, pres 1, def32 1, gran 1 > Mar 6 10:12:45 mx0 /kernel: processor eflags = interrupt enabled, resume, > IOPL = 0 > Mar 6 10:12:45 mx0 /kernel: current process = 6 (vnlru) > Mar 6 10:12:45 mx0 /kernel: interrupt mask = bio <- SMP: XXX > Mar 6 10:12:45 mx0 /kernel: trap number = 12 > Mar 6 10:12:45 mx0 /kernel: panic: page fault > Mar 6 10:12:45 mx0 /kernel: mp_lock = 03000002; cpuid = 3; lapic.id = > 03000000 > Mar 6 10:12:45 mx0 /kernel: boot() called on cpu#3 > Mar 6 10:12:45 mx0 /kernel: > Mar 6 10:12:45 mx0 /kernel: syncing disks... 84 3 3 3 3 3 3 3 34 > Mar 6 10:12:45 mx0 /kernel: done > Mar 6 10:12:45 mx0 /kernel: Uptime: 3h8m39s > Mar 6 10:12:45 mx0 /kernel: Automatic reboot in 15 seconds - press a key on > the console to abort > Mar 6 10:12:45 mx0 /kernel: Rebooting... > Mar 6 10:12:45 mx0 /kernel: cpu_reset called on cpu#3 > Mar 6 10:12:45 mx0 /kernel: cpu_reset: Stopping other CPUs > Mar 6 10:12:45 mx0 /kernel: cpu_reset: Restarting BSP > Mar 6 10:12:45 mx0 /kernel: cpu_reset_proxy: Gcrpaub_breeds emtp: lBoScPk > dfiodr nBoStP > Mar 6 10:12:45 mx0 /kernel: grab mp lock > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?006101c2e41a$58238280$0200a8c0>