Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 Mar 2001 12:52:11 -0600 (CST)
From:      Tom Duffey <tduffey@wi.rr.com>
To:        John Baldwin <jhb@FreeBSD.org>
Cc:        freebsd-smp@FreeBSD.org
Subject:   RE: More detailed debugging info for Netfinity SMP lock
Message-ID:  <Pine.LNX.4.21.0103241243490.1659-100000@linuxpower.p00t.net>
In-Reply-To: <XFMail.010323182608.jhb@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Here's the trace, taken directly after the panic shown below.  Hopefully
I'm doing this right ...

db> trace
Debugger(c0x798d2) at Debugger+0x34
panic(c0258f5a,1,c02e3140,10000001,c024a26b) at panic+0xa4
bsl1(0,a0,0) at bsl1
selected_apic_ipi(1,a0,0,a,ff80dee8) at selected_apic_ipi+0x3a
stop_cpus(1,0,0,1,ff80df34) at stop_cpus+0x21
kdb_trap(a,0,ff80df3c) at kdb_trap+0xe5
trap(18,10,10,ff80a864,0) at trap+0x454
calltrap() at calltrap+0x17
--- trap 0xa, eip = 0xc0258f2d, esp = 0xff80df7c, ebp = 0xff80dfdc
setlock(3a60000,0,0,1,0) at setlock+0x11
vm_page_zero_idle(c02596c4,

Fatal trap 12: page fault while in kernel mode
mp_lock = 01000007; cpuid = 1, lapic.id = 00000000
fault virtual address	= 0xff80e000
fault code		= supervisor read, page not present
instruction pointer	= 0x8:0xc0247c30
stack pointer		= 0x10:0xff80dbc8
frame pointer		= 0x10:0xff80dbcc
code segment		= hbase 0x0, limit 0xfffff, type 0x1b
			= DPL 0, pres 1, defs32 1, gran 1
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= Idle
interrupt mask		= tty <- SMP: XXX
kernel: type 12 trap, code 0

Let me know if I've done something incorrectly or missed anything.

Thanks,

Tom Duffey

On Fri, 23 Mar 2001, John Baldwin wrote:

> 
> On 23-Mar-01 Tom Duffey wrote:
> > Thanks to everyone for the help so far.  This morning I upgraded the
> > system BIOS to the latest provided by IBM (v1.06) but still cannot boot
> > the system with an SMP enabled kernel.  However, I enabled the kernel
> > debugger and came up with the following:
> > 
> > stopped at    atkbd_isa_intr+0x19;    ret
> > stopped at    Xresume1+0x35:          cli
> > stopped at    Xresume1+0x36:          lock andl $-0x3,iactive
> > stopped at    Xresume1+0x3e:          pushl $0xc02e3140
> > stopped at    Xresume1+0x43:          call s_lock
> > stopped at    s_lock:                 movel 0x4(%esp),$edx
> > stopped at    setlock:                movel %fs:0x94,%ecx
> > stopped at    setlock+0x7:            incl %ecx
> > stopped at    setlock+0x8:            movl $0,%eax
> > stopped at    setlock+0xd:            lock cmpxchgl %ecx,0(%edx)
> > panic: rslock: cpu: 1, addr 0xc02e3140, lock: 0x01000001
> > mp_lock = 01000003; cpuid = 1; lapic.id = 00000000
> > Debugger("panic")
> > Stopped at    Debugger+0x34:          movb $0,in_Debugger,597
> > db>
> 
> Type 'trace' here to see where we are.  It is recursing on a simplelock which
> is very bad.  It is probably a kernel bug but could be something else.
> 
> -- 
> 
> 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-smp" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.21.0103241243490.1659-100000>