Re: Trace for rpcbind panic
This is the same backtrace I got when I tried it too... The system would get all the way through booting, then fam (I'm assuming) sent something to rpcbind, which then caused this panic. Ken On Mon, 14 Jan 2002, Michael McGoldrick wrote: > The trace was short, so I wrote the whole thing down. > > _mtx_unlock_sleep(c232c834,0,0,0) at _mtx_unlock_sleep+0x9f > unp_externalize(c0b6ab00,c0b6ac00,cb5d3ccc,cb5d3c8c,cb5d3ccc) at unp_externalize > +0x38e > soreceive(ca29d420,cb5d3c18,cb5d3c44,0,cb5d3c1c) at soreceive+0x376 > recvit(ca284304,b,cb5d3ccc,0,ca284200) at recvit+0x121 > recvmsg(ca284304,cb5d3d20,281221c8,bfbfd550,2328) at recvmsg+0xdb > syscall(2f,2f,2f,2328,bfbfd550) at syscall+0x2d4 > syscall_with_err_pushed() at syscall_with_err_pushed+0x1b > --- syscall(27, FreeBSD ELF, recvmsg), eip=0x280c0657, esp=0xbfbfd500, ebp=0xbfb > fd5cc --- > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rpcbind panic
I can second this. I have seen the same panic, but was too lazy to hand copy it. Ken On Mon, 14 Jan 2002, Michael McGoldrick wrote: > Kernel and world built with sources cvsupped as of Mon Jan 14 18:44:04 GMT from > cvsup.freebsd.org. > The panic message is hand copied. Please send me a mail if other details (eg dme > sg) are required. > > Kernel trap 12 with interrupts disabled > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x28 > fault code= supervisor read, page not present > instruction pointer = 0x8:0xc01d9f07 > stack pointer = 0x10:0xcb5b8b4c > frame pointer = 0x10:0xcb5b8b5c > code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 178 (rpcbind) > kernel: type 12 trap, code = 0 > stopped at _mtx_unlock_sleep+0x9f : cmpl $0,0x28(%ebx) > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Trace for rpcbind panic
On 14-Jan-02 Michael McGoldrick wrote: > The trace was short, so I wrote the whole thing down. That one is fixed already, re-cvsup. Also, you should probably be running with INVARIANTS turned on in -current as that would give more useful error messages. > _mtx_unlock_sleep(c232c834,0,0,0) at _mtx_unlock_sleep+0x9f > unp_externalize(c0b6ab00,c0b6ac00,cb5d3ccc,cb5d3c8c,cb5d3ccc) at > unp_externalize > +0x38e > soreceive(ca29d420,cb5d3c18,cb5d3c44,0,cb5d3c1c) at soreceive+0x376 > recvit(ca284304,b,cb5d3ccc,0,ca284200) at recvit+0x121 > recvmsg(ca284304,cb5d3d20,281221c8,bfbfd550,2328) at recvmsg+0xdb > syscall(2f,2f,2f,2328,bfbfd550) at syscall+0x2d4 > syscall_with_err_pushed() at syscall_with_err_pushed+0x1b > --- syscall(27, FreeBSD ELF, recvmsg), eip=0x280c0657, esp=0xbfbfd500, > ebp=0xbfb > fd5cc --- -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "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
Trace for rpcbind panic
The trace was short, so I wrote the whole thing down. _mtx_unlock_sleep(c232c834,0,0,0) at _mtx_unlock_sleep+0x9f unp_externalize(c0b6ab00,c0b6ac00,cb5d3ccc,cb5d3c8c,cb5d3ccc) at unp_externalize +0x38e soreceive(ca29d420,cb5d3c18,cb5d3c44,0,cb5d3c1c) at soreceive+0x376 recvit(ca284304,b,cb5d3ccc,0,ca284200) at recvit+0x121 recvmsg(ca284304,cb5d3d20,281221c8,bfbfd550,2328) at recvmsg+0xdb syscall(2f,2f,2f,2328,bfbfd550) at syscall+0x2d4 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall(27, FreeBSD ELF, recvmsg), eip=0x280c0657, esp=0xbfbfd500, ebp=0xbfb fd5cc --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: rpcbind panic
On 14-Jan-02 Michael McGoldrick wrote: > Kernel and world built with sources cvsupped as of Mon Jan 14 18:44:04 GMT > from > cvsup.freebsd.org. > The panic message is hand copied. Please send me a mail if other details (eg > dme > sg) are required. A traceback would be most useful. Type 't' in ddb. And just give the list of function names and the first arg for each function please. > Kernel trap 12 with interrupts disabled > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x28 > fault code= supervisor read, page not present > instruction pointer = 0x8:0xc01d9f07 > stack pointer = 0x10:0xcb5b8b4c > frame pointer = 0x10:0xcb5b8b5c > code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 178 (rpcbind) > kernel: type 12 trap, code = 0 > stopped at _mtx_unlock_sleep+0x9f : cmpl $0,0x28(%ebx) > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "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
rpcbind panic
Kernel and world built with sources cvsupped as of Mon Jan 14 18:44:04 GMT from cvsup.freebsd.org. The panic message is hand copied. Please send me a mail if other details (eg dme sg) are required. Kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0x28 fault code= supervisor read, page not present instruction pointer = 0x8:0xc01d9f07 stack pointer = 0x10:0xcb5b8b4c frame pointer = 0x10:0xcb5b8b5c code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 178 (rpcbind) kernel: type 12 trap, code = 0 stopped at _mtx_unlock_sleep+0x9f : cmpl $0,0x28(%ebx) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
