Date: Wed, 06 Dec 2000 21:10:34 -0800 From: Manfred Antar <null@pozo.com> To: John Baldwin <jhb@FreeBSD.ORG>, current@FreeBSD.ORG Subject: RE: Current kernel build failure -- >>cam_periph.c Message-ID: <5.0.2.1.2.20001206210835.00ada270@pozo.com> In-Reply-To: <XFMail.001206182818.jhb@FreeBSD.org> References: <XFMail.001206174948.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.0.2.1.2.20001206210835.00ada270>