Date: Wed, 12 Nov 2008 20:57:17 GMT From: Thad Schulz <tschulz@sebeka.k12.mn.us> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/128829: smbd causes periodic panic on 7-RELEASE Message-ID: <200811122057.mACKvHtX021397@www.freebsd.org> Resent-Message-ID: <200811122100.mACL0CbC056733@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 128829 >Category: kern >Synopsis: smbd causes periodic panic on 7-RELEASE >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Nov 12 21:00:12 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Thad Schulz >Release: 7-RELEASE >Organization: Sebeka Public School >Environment: FreeBSD nat.menahga.k12.mn.us 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >Description: smbd seems to produce a kernel panic under high load mostly during logins. The server seems to panic infrequently between twice a day to a once every two weeks. This is the backtrace of the core dump Unread portion of the kernel message buffer: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 06 fault virtual address = 0x29 fault code = supervisor write, protection violation instruction pointer = 0x20:0xc0744a51 stack pointer = 0x28:0xf1b10b30 frame pointer = 0x28:0xf1b10b88 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 56651 (smbd) trap number = 12 panic: page fault cpuid = 2 Uptime: 5d21h19m55s Physical memory: 3571 MB Dumping 333 MB: 318 302 286 270 254 238 222 206 190 174 158 142 126 110 94 78 62 46 30 14 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc0754457 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0xc0754719 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xc0a4905c in trap_fatal (frame=0xf1b10af0, eva=41) at /usr/src/sys/i386/i386/trap.c:899 #4 0xc0a499df in trap (frame=0xf1b10af0) at /usr/src/sys/i386/i386/trap.c:280 #5 0xc0a2fc0b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #6 0xc0744a51 in lf_advlock (ap=0xf1b10c20, head=0xccde44d8, size=3956736) at atomic.h:149 #7 0xc095d7ad in ufs_advlock (ap=0xf1b10c20) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2181 #8 0xc0a5e1e7 in VOP_ADVLOCK_APV (vop=0xc0b93c60, a=0xf1b10c20) at vnode_if.c:1977 #9 0xc0729547 in kern_fcntl (td=0xc7b20210, fd=13, cmd=9, arg=-240055200) at vnode_if.h:1036 #10 0xc0729e07 in fcntl (td=0xc7b20210, uap=0xf1b10cfc) at /usr/src/sys/kern/kern_descrip.c:336 #11 0xc0a49635 in syscall (frame=0xf1b10d38) at /usr/src/sys/i386/i386/trap.c:1035 #12 0xc0a2fc70 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:196 #13 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) >How-To-Repeat: smbd seems to produce a kernel panic under high load mostly during logins. The server seems to panic infrequently between twice a day to a once every two weeks. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200811122057.mACKvHtX021397>