Date: Thu, 07 Dec 2000 16:40:02 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: Manfred Antar <null@pozo.com> Cc: current@FreeBSD.org Subject: RE: Current kernel build failure -- >>cam_periph.c Message-ID: <XFMail.001207164002.jhb@FreeBSD.org> In-Reply-To: <5.0.2.1.2.20001206210835.00ada270@pozo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07-Dec-00 Manfred Antar wrote: > 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 Hmmmmmm. I haven't reproduced this here. Let me play with it some more. -- John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ 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?XFMail.001207164002.jhb>