From owner-freebsd-current Wed Dec 6 21:10:43 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 21:10:40 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 25D9337B400; Wed, 6 Dec 2000 21:10:40 -0800 (PST) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.1/8.11.1) with ESMTP id eB75AYE00341; Wed, 6 Dec 2000 21:10:35 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <5.0.2.1.2.20001206210835.00ada270@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Wed, 06 Dec 2000 21:10:34 -0800 To: John Baldwin , current@FreeBSD.ORG From: Manfred Antar Subject: RE: Current kernel build failure -- >>cam_periph.c In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 06:28 PM 12/6/2000 -0800, John Baldwin wrote: >On 07-Dec-00 John Baldwin wrote: >> >> On 07-Dec-00 Manfred Antar wrote: >>> >>> >>> I've been trying to build a current kernel from current sources for a day >>> now >>> and I keep getting this: >> >> I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() >> compiles in dozens of other places just fine (and has for months now). > >Nope, it was a sublte bug in the 486 optimized mutex operations, which had >invalid register constraints probably dating back to several older revisions in >BSD/OS before we got the code. It should be fixed now. > John It compiles now fine but panics on booting: Doing initial network setup: hostname. panic: mutex sched lock owned at ../../kern/kern_mutex.c:322 cpuid = 0; lapic.id = 00000000 boot() called on cpu#0 syncing disks... Fatal double fault: eip = 0xc02b0e7d esp = 0xcafce000 ebp = 0xcafce020 cpuid = 0; lapic.id = 00000000 I built another one and got a different panic: Initial rc.i386 panic: spin lock sched lock held by 0x0xc0390a01 for > 5 seconds cpuid = 1; lapic.id = 0c000000 boot() called on cpu#1 syncing disks... Just frozen at this point Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message