Re: kernel broken? (devfs maybe?)
that fixes it.. thanks On Fri, 25 Oct 2002, Poul-Henning Kamp wrote: > > Please try the rev 1.418 of vfs_subr.c > > >> db> tr > >> v_incr_usecount(c1d76cb8,,c037b472,863,cc34a92c) at > >> v_incr_usecount+0x48vrele(c1d76cb8,c1c90a00,c036cc7a,6,100) at > >> vrele+0xb0 > >> addaliasu(c1d76cb8,402,c1cb6200,cc34a9c0,c1d73b00) at addaliasu+0x1ad > >> devfs_allocv(c1d8f880,c1c90a00,cc34ac38,c0f26340,c01e6fe0) at > >> devfs_allocv+0xee > >> devfs_lookupx(cc34ab50,1,0,c0f26340,6) at devfs_lookupx+0x58f > >> devfs_lookup(cc34ab50,c0f26340,0,c0f26340,c037b472) at devfs_lookup+0x4b > >> lookup(cc34ac24,0,c037ad9a,a4,cc34abb8) at lookup+0x302 > >> namei(cc34ac24,c01bb4bd,c03fbac0,1,c037264a) at namei+0x24e > >> stat(c0f26340,cc34ad10,c039bed6,409,2) at stat+0x52 > >> syscall(2f,2f,2f,8057e86,805b52f) at syscall+0x28e > >> Xint0x80_syscall() at Xint0x80_syscall+0x1d > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > [EMAIL PROTECTED] | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel broken? (devfs maybe?)
Please try the rev 1.418 of vfs_subr.c >> db> tr >> v_incr_usecount(c1d76cb8,,c037b472,863,cc34a92c) at >> v_incr_usecount+0x48vrele(c1d76cb8,c1c90a00,c036cc7a,6,100) at >> vrele+0xb0 >> addaliasu(c1d76cb8,402,c1cb6200,cc34a9c0,c1d73b00) at addaliasu+0x1ad >> devfs_allocv(c1d8f880,c1c90a00,cc34ac38,c0f26340,c01e6fe0) at >> devfs_allocv+0xee >> devfs_lookupx(cc34ab50,1,0,c0f26340,6) at devfs_lookupx+0x58f >> devfs_lookup(cc34ab50,c0f26340,0,c0f26340,c037b472) at devfs_lookup+0x4b >> lookup(cc34ac24,0,c037ad9a,a4,cc34abb8) at lookup+0x302 >> namei(cc34ac24,c01bb4bd,c03fbac0,1,c037264a) at namei+0x24e >> stat(c0f26340,cc34ad10,c039bed6,409,2) at stat+0x52 >> syscall(2f,2f,2f,8057e86,805b52f) at syscall+0x28e >> Xint0x80_syscall() at Xint0x80_syscall+0x1d -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Re: kernel broken? (devfs maybe?)
yep that fixes it.. On Thu, 24 Oct 2002, Andrew Gallatin wrote: > > Try backing out phk's src/sys/kern/vfs_subr.c 1.416 > Does that help? > > Drew > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Re: kernel broken? (devfs maybe?)
Try backing out phk's src/sys/kern/vfs_subr.c 1.416 Does that help? Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel broken? (devfs maybe?)
nope.. not mine..(just backed everything out here and retested.. still got it..) don't know if the lock reversal is related... That may be an orthogonal bug.. On Thu, 24 Oct 2002, Julian Elischer wrote: > > I thought this might be one on mine, but > it doesn't look like mine.. > > (I'm busy recompiling a version with my latest changes backed out > to check though.. in the mean while.. if anyone wants to claim > this) > > IPsec: Initialized Security Association Processing. > ad0: 9541MB [19386/16/63] at ata0-master UDMA100 > acd0: CDROM at ata1-master PIO4 > Mounting root from ufs:/dev/ad0s1a > Enter full pathname of shell or RETURN for /bin/sh: > # fsck -p > lock order reversal > 1st 0xc0420400 spechash (spechash) @ ../../../kern/vfs_subr.c:1962 > 2nd 0xc1d6f228 process lock (process lock) @ > ../../../i386/i386/trap.c:731 > > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x78 > fault code= supervisor write, page not present > instruction pointer = 0x8:0xc0217f58 > stack pointer = 0x10:0xcc34a8d8 > frame pointer = 0x10:0xcc34a8f0 > code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 42 (fsck) > kernel: type 12 trap, code=0 > Stopped at v_incr_usecount+0x48: addl%esi,0x78(%eax) > db> Context switches not allowed in the debugger. > db> tr > v_incr_usecount(c1d76cb8,,c037b472,863,cc34a92c) at > v_incr_usecount+0x48vrele(c1d76cb8,c1c90a00,c036cc7a,6,100) at > vrele+0xb0 > addaliasu(c1d76cb8,402,c1cb6200,cc34a9c0,c1d73b00) at addaliasu+0x1ad > devfs_allocv(c1d8f880,c1c90a00,cc34ac38,c0f26340,c01e6fe0) at > devfs_allocv+0xee > devfs_lookupx(cc34ab50,1,0,c0f26340,6) at devfs_lookupx+0x58f > devfs_lookup(cc34ab50,c0f26340,0,c0f26340,c037b472) at devfs_lookup+0x4b > lookup(cc34ac24,0,c037ad9a,a4,cc34abb8) at lookup+0x302 > namei(cc34ac24,c01bb4bd,c03fbac0,1,c037264a) at namei+0x24e > stat(c0f26340,cc34ad10,c039bed6,409,2) at stat+0x52 > syscall(2f,2f,2f,8057e86,805b52f) at syscall+0x28e > Xint0x80_syscall() at Xint0x80_syscall+0x1d > > > > > > 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
