Re: panic in prison_check

On Tue, 17 Aug 2004, Pawel Worach wrote:

> #9  0xc04e0010 in prison_check (cred1=0xc1c63e74, cred2=0x41211cd6)
>      at /usr/src/sys/kern/kern_jail.c:402

Looks like the second pointer here is bad...

I'm having trouble finding a calling path from selwakeuppri() to
prison_check().

> #10 0xc0523768 in selwakeuppri (sip=0x0, pri=0)
>      at /usr/src/sys/kern/sys_generic.c:1096

And the first pointer here is NULL..?

> #11 0xc053300c in ttwakeup (tp=0xc1c63e00) at /usr/src/sys/kern/tty.c:2366

This seems like a reasonable pointer.  Would be interesting to know what
*tp looks like.

> #12 0xc05318dc in ttymodem (tp=0xc1c63e00, flag=0)
>      at /usr/src/sys/kern/tty.c:1625
> #13 0xc0536487 in ptcopen (dev=0xc1cc4d00, flag=3, devtype=8192, td=0x0)
>      at linedisc.h:136
> #14 0xc04b570a in spec_open (ap=0xcd35aa70)
>      at /usr/src/sys/fs/specfs/spec_vnops.c:207
> #15 0xc04b53b8 in spec_vnoperate (ap=0x0)
>      at /usr/src/sys/fs/specfs/spec_vnops.c:118
> #16 0xc056eb8e in vn_open_cred (ndp=0xcd35abd8, flagp=0xcd35acd8, cmode=0,
>      cred=0xc1d12780, fdidx=0) at vnode_if.h:228
> #17 0xc056e723 in vn_open (ndp=0x0, flagp=0x0, cmode=0, fdidx=0)
>      at /usr/src/sys/kern/vfs_vnops.c:91
> #18 0xc0567383 in kern_open (td=0xc197dc60, path=0x0, 
> pathseg=UIO_USERSPACE,
>      flags=3, mode=0) at /usr/src/sys/kern/vfs_syscalls.c:957
> #19 0xc0567260 in open (td=0x0, uap=0x0)
>      at /usr/src/sys/kern/vfs_syscalls.c:926
> #20 0xc0681040 in syscall (frame=
>        {tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 134795403, tf_esi = 
> 134795392, tf_ebp = -1077946760, tf_isp = -852120204, tf_ebx = 
> 134795264, tf_edx = 11, tf_ecx = 11, tf_eax = 5, tf_trapno = 22, tf_err 
> = 2, tf_eip = 675104111, tf_cs = 31, tf_eflags = 518, tf_esp = 
> -1077946804, tf_ss = 47})
>      at /usr/src/sys/i386/i386/trap.c:1004
> #21 0xc0670f4f in Xint0x80_syscall () at 
> /usr/src/sys/i386/i386/exception.s:201
> #22 0x0000002f in ?? ()
> #23 0x0000002f in ?? ()
> #24 0x0000002f in ?? ()
> #25 0x0808d08b in ?? ()
> #26 0x0808d080 in ?? ()
> #27 0xbfbfd678 in ?? ()
> #28 0xcd35ad74 in ?? ()
> #29 0x0808d000 in ?? ()
> #30 0x0000000b in ?? ()
> #31 0x0000000b in ?? ()
> #32 0x00000005 in ?? ()
> #33 0x00000016 in ?? ()
> #34 0x00000002 in ?? ()
> #35 0x283d456f in ?? ()
> #36 0x0000001f in ?? ()
> #37 0x00000206 in ?? ()
> #38 0xbfbfd64c in ?? ()
> #39 0x0000002f in ?? ()
> #40 0x00000000 in ?? ()
> #41 0x00000000 in ?? ()
> #42 0x00000000 in ?? ()
> #43 0x00000000 in ?? ()
> #44 0x0e8bc000 in ?? ()
> #45 0xc155f9a0 in ?? ()
> ---Type <return> to continue, or q <return> to quit---
> #46 0xc15e3cd0 in ?? ()
> #47 0xcd35aca4 in ?? ()
> #48 0xcd35ac84 in ?? ()
> #49 0xc197dc60 in ?? ()
> #50 0xc050dd90 in sched_switch (td=0x808d000, newtd=0x808d08b)
>      at /usr/src/sys/kern/sched_ule.c:1207
> Previous frame inner to this frame (corrupt stack?)
> (kgdb) p panicstr
> $1 = 0xc06fe560 "page fault"
> 
> vmcore and kernel.debug is saved if more info is requested.
> 
> -- 
> Pawel
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>