From owner-freebsd-smp Fri Jan 15 12:26:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06207 for freebsd-smp-outgoing; Fri, 15 Jan 1999 12:26:58 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from psv.oss.uswest.net (psv.oss.uswest.net [204.147.85.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06189; Fri, 15 Jan 1999 12:26:55 -0800 (PST) (envelope-from greg@psv.oss.uswest.net) Received: (from greg@localhost) by psv.oss.uswest.net (8.8.8/8.8.5) id OAA13011; Fri, 15 Jan 1999 14:26:47 -0600 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 15 Jan 1999 14:26:46 -0600 (CST) Reply-To: greg@uswest.net Organization: US WEST !NTERACT From: Greg Rowe To: freebsd-smp@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: More - Fatal Trap - Update Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I found today that cpio will also cause the crash in the exact same way. It's interesting that bonnie won't though since that's what we usually use to test for IO problems. Greg -----FW: Fatal Trap - Update----- Date: Thu, 14 Jan 1999 15:05:17 -0600 (CST) From: Greg Rowe To: freebsd-smp@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Fatal Trap - Update I've done some more testing on this problem and have at least narrowed it down somewhat. The failure happens repeatedly by just un-tarring a tar file. No matter what the tar file contains, it seems to always drop into the debbugger at approximately the same point in the file ??? I've done this around 30 times with different tar files and it always crashes within a file or two of the previous crash. It seems to only be able to handle X amount of IO from tar, but multiple copies of bonnie run fine. The problem doesn't seem to be hardware related (at least failing hardware) as it happens on another system with the same mainboard and CPU's. The problem does not happen in non-SMP mode. The problem also does not exist in SMP mode on 3.0-RELEASE (straight CD install with SMP-GENERIC kernel), so the problem was introduced in -CURRENT. (I'm running yesterdays -CURRENT now) Adaptec SCSI controller revision, number of drives, type of drives, and number of controllers do not effect the problem, I've tried it all ways. Also, the page fault will sometimes report cpuid=0 and sometimes cpuid=1. The problem doesn't exist on a quad Xeon system running the same -CURRENT. So, I guess the question of the day is "what does a Tyan Tiger 100 mainboard, 3.0 CURRENT, SMP, and tar have in common" ? Any ideas what I should try next ? Thanks, Greg -----FW: Fatal Trap----- Date: Mon, 11 Jan 1999 16:48:53 -0600 (CST) From: Greg Rowe To: freebsd-scsi@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Fatal Trap I have a Tyan mb dual 400mhz system I'm building that's getting repeatable crashes under disk load. This didn't occur until I compiled an SMP kernel. I'm running -current as of last Friday and the system has 512mb of memory and 4 drives on Adaptec controllers (1 - 4gig on one controller and 3 - 9gig on the other). Untarring a file will interestingly enough crash the system at around the same appoximate place in the tar image every time, although it's crashed while building ports also. The system drops to the debugger with the following: Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid=1; lapic.id = 01000000(I've also seen it for cpuid0) fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xf0216357 stack pointer = 0x10:0xff618ce8 frame pointer = 0x10:0xff618d0c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 243 (tar) interrupt mask = net tty bio cam <-SMP:XXX kernel: type 12 trap, code 0 Stopped at generic_bzero+0xf: repe stosl %es:(%edi) Any ideas as to what to look for ? Thanks. Greg --------------End of forwarded message------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message