From owner-freebsd-bugs Wed Mar 7 14:46:48 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from texorami.ghostwheel.com (texorami.ghostwheel.com [209.21.75.126]) by hub.freebsd.org (Postfix) with ESMTP id 7029D37B71A for ; Wed, 7 Mar 2001 14:46:43 -0800 (PST) (envelope-from merlin@ghostwheel.com) Received: from avalon.ghostwheel.com (97bus23.tampabay.rr.com [24.94.97.23]) by texorami.ghostwheel.com (8.9.3/8.9.3) with ESMTP id OAA46598 for ; Wed, 7 Mar 2001 14:46:43 -0800 (PST) (envelope-from merlin@ghostwheel.com) Message-Id: <5.1.0.10.0.20010307144750.02119938@imap2.ghostwheel.com> X-Sender: merlin.mail@imap2.ghostwheel.com X-Mailer: QUALCOMM Windows Eudora Version 5.1.0.10 (Beta) Date: Wed, 07 Mar 2001 14:47:56 -0800 To: freebsd-bugs@freeBSD.org From: Christopher Knight Subject: NMI blowout during make buildworld. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My system: P3-550/256M SDRAM (possibly ECC) Intel SE44BX-2 motherboard with p17 BIOS IDE boot disk with a vinum mirror for my webspace Adaptec 2940 Ultra SCSI adapter 3Com 3c905B-TX Fast Etherlink XL The OS is FreeBSD 4.3-BETA. I have been having crashes during make buildworld lately, so I wound up building a new kernel today. The kernel is up-to-date while the rest of the system is out of sync by a few weeks. Here is what I got on the serial console today while running a buildworld: Fatal trap 19: non-maskable interrupt trap while in kernel mode instruction pointer = 0x8:0xc025ffdc stack pointer = 0x10:0xd2c4edb4 frame pointer = 0x10:0xd2c4ede4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 57014 (cpp) interrupt mask = none trap number = 19 panic: non-maskable interrupt trap syncing disks... 133 132 119 103 79 50 21 1 1 1 1 1 1 1 1 1 1 1 1 1 done Uptime: 1h0m22s Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Any and all assistance appreciated! The machine is in a co-lo facility 3000 miles away... If I can fix this from remote, great. If it looks like a hardware problem I want to be able to get it fixed on the first pass. :) If there is any other information I can provide, just let me know. Thanks! -ck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message