RE: Current kernel build failure -- >>cam_periph.c
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 = > boot() called on cpu#0 Hmm. I haven't reproduced this here. Let me play with it some more. -- John Baldwin <[EMAIL PROTECTED]> -- 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Current kernel build failure -- >>cam_periph.c
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 = boot() called on cpu#0 syncing disks... Fatal double fault: eip = 0xc02b0e7d esp = 0xcafce000 ebp = 0xcafce020 cpuid = 0; lapic.id = 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 = 0c00 boot() called on cpu#1 syncing disks... Just frozen at this point Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Current kernel build failure -- >>cam_periph.c
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 Baldwin <[EMAIL PROTECTED]> -- 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current kernel build failure -- >>cam_periph.c
On Wed, Dec 06, 2000 at 06:13:50PM -0800, Manfred Antar wrote: # At 05:49 PM 12/6/2000 -0800, you wrote: # # >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). # # Yes # It's a different kind of error. # I've never seen this building a kernel before. # The same kernel config without SMP enabled builds fine ! At least according to my tests thus far it appears it occurs when 'cpu I386_CPU' is not in your config file. It isn't really an SMP issue as far as I can tell, except that you must remove 'cpu I386_CPU' to build an SMP kernel. -steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Current kernel build failure -- >>cam_periph.c
At 05:49 PM 12/6/2000 -0800, you 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). > >-- > >John Baldwin <[EMAIL PROTECTED]> -- 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 [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message Yes It's a different kind of error. I've never seen this building a kernel before. The same kernel config without SMP enabled builds fine ! == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Current kernel build failure -- >>cam_periph.c
On Wed, 6 Dec 2000, 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). ah, so I take it a 'make buildworld' doesn't fix thsi one :) ah well, had to do it anyway ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Current kernel build failure -- >>cam_periph.c
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). -- John Baldwin <[EMAIL PROTECTED]> -- 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
