From owner-freebsd-current@FreeBSD.ORG Fri Mar 28 18:34:32 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8080A37B401 for ; Fri, 28 Mar 2003 18:34:32 -0800 (PST) Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBB5E43FBD for ; Fri, 28 Mar 2003 18:34:31 -0800 (PST) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) by bunrab.catwhisker.org (8.12.8/8.12.8) with ESMTP id h2T2YVhw020714 for ; Fri, 28 Mar 2003 18:34:31 -0800 (PST) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.12.8/8.12.8/Submit) id h2T2YVXP020713 for current@freebsd.org; Fri, 28 Mar 2003 18:34:31 -0800 (PST) Date: Fri, 28 Mar 2003 18:34:31 -0800 (PST) From: David Wolfskill Message-Id: <200303290234.h2T2YVXP020713@bunrab.catwhisker.org> To: current@freebsd.org In-Reply-To: <200303281646.h2SGkd9m019357@bunrab.catwhisker.org> Subject: Re: Fatal trap 9: general protection fault while in kernel mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Mar 2003 02:34:34 -0000 >Date: Fri, 28 Mar 2003 08:46:39 -0800 (PST) >From: David Wolfskill [Yes, I'm responding to my own post....] >Got -CURRENT (re-)built; booted, logged in, poked around, seemed OK; >issued: > sudo boot0cfg -s 1 ad0 && sudo halt -p >(to switch to default to booting from -STABLE next time I bring the >machine up, then power the machine off). >Was greeted on the xterm that has the serial console by: >... >r system process `bufdaemon' to stop... >Fatal trap 9: general protection fault while in kernel mode >cpuid = 1; lapic.id = 01000000 >instruction pointer = 0x8:0xd68e2d0a >stack pointer = 0x10:0xd68e2ce4 >frame pointer = 0x10:0x8 >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 = 11 (idle: cpu1)stopped >r' to stop...60 seconds) for system process `synce >kernel: type 9 trap, code=0 >Stopped at 0xd68e2d0a: mov %si,%ss >db> tr >.... >As you can see, the box is SMP (2x886 MHz PIIIs); 512 MB RAM iirc. Very >little customization for the kernel beyond tweaking GENERIC for SMP. >I'm presently building -CURRENT from equivalent sources on my (UP) >laptop. Interestingly enough, I had no problems at all on my laptop. Each machine has a single ATA disk drive; other than /tmp (which is a swap-backed md memory disk), all mounted file systems are UFS (not UFS2); each UFS file system [that sounds redundant...] has soft updates enabled. I just tried telling kdb to panic, and got: db> panic panic: from debugger cpuid = 1; lapic.id = 01000000 Debugger("panic") Fatal trap 3: breakpoint instruction fault while in kernel mode cpuid = 1; lapic.id = 01000000 instruction pointer = 0x8:0xc0341ba5 stack pointer = 0x10:0xd68e2a8c frame pointer = 0x10:0xd68e2a98 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = IOPL = 0 current process = 11 (idle: cpu1) Stopped at 0xd68e2d0a: mov %si,%ss db> Peace, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill david@catwhisker.org Based on what I have seen to date, the use of Microsoft products is not consistent with reliability. I recommend FreeBSD for reliable systems.