Re: panic in RELENG_5 UMA

From: Gleb Smirnoff (glebius_at_FreeBSD.org)
Date: 06/27/05

  • Next message: Kövesdán Gábor: "bsdextended mac module question" 
    Date: Mon, 27 Jun 2005 12:29:58 +0400
To: Gary Mu1der <gmulder@infotechfl.com>

    On Fri, Jun 24, 2005 at 03:28:34PM -0400, Gary Mu1der wrote:
    G> Can someone confirm that the following stack trace is showing the same
    G> problem, or not?
    G> I can reproduce the problem with the custom kernel config included below
    G> (which is basically GENERIC stripped of devices I don't have or need and
    G> IPFILTER added), but not with a stock GENERIC kernel.
    G>
    G> To cause the crash I'm running 20-30 instances of the following script:
    G>
    G> d5# cat arping.sh
    G> #!/bin/sh
    G>
    G> while :
    G> do
    G> arp -d 192.168.4.$1 >/dev/null 2>&1;
    G> ping -c 1 -t 1 192.168.4.$1 >/dev/null 2>&1;
    G> done

    When running without INVARIANTS, it is much more difficult to analyze panics.
    If this script drops your kernel to panic, then it is very likely that
    it is the same problem.

    Can you please provide the following info:

    G> (kgdb) bt
    G> #0 doadump () at pcpu.h:167
    G> #1 0x0000000000000000 in ?? ()
    G> #2 0xffffffff802557b7 in boot (howto=260) at
    G> /usr/src/sys/kern/kern_shutdown.c:410
    G> #3 0xffffffff80255fef in panic (fmt=0xffffff00b5907500 " ?6?")
    G> at /usr/src/sys/kern/kern_shutdown.c:566

    (kgdb) p *panicstr

    G> #4 0xffffffff8029ad2a in sbdrop_locked (sb=0xffffffffb6274860, len=1146)
    G> at /usr/src/sys/kern/uipc_socket2.c:1149

    (kgdb) frame 4
    (kgdb) ls
    (kgdb) p *m

    G> #5 0xffffffff8029afe2 in sbflush_locked (sb=0xffffffffb6274860)
    G> at /usr/src/sys/kern/uipc_socket2.c:1116
    G> #6 0xffffffff8029b049 in sbrelease_locked (sb=0xffffffffb6274860,
    G> so=0xffffff00a0a2a8a0)
    G> at /usr/src/sys/kern/uipc_socket2.c:564
    G> #7 0xffffffff8029b0d5 in sbrelease (sb=0xffffffffb6274860,
    G> so=0xffffff00a0a2a8a0)
    G> at /usr/src/sys/kern/uipc_socket2.c:577
    G> #8 0xffffffff80297b03 in sorflush (so=0xffffff00a0a2a8a0)
    G> at /usr/src/sys/kern/uipc_socket.c:1483
    G> #9 0xffffffff80297e42 in sofree (so=0xffffff00a0a2a8a0) at
    G> /usr/src/sys/kern/uipc_socket.c:407
    G> #10 0xffffffff80298467 in soclose (so=0xffffff00a0a2a8a0) at
    G> /usr/src/sys/kern/uipc_socket.c:485
    G> #11 0xffffffff802847b5 in soo_close (fp=0xffffff009ca95b60, td=0x0)
    G> at /usr/src/sys/kern/sys_socket.c:299
    G> #12 0xffffffff8022c2c0 in fdrop_locked (fp=0xffffff009ca95b60,
    G> td=0xffffff00b5907500)
    G> at file.h:288

    (kgdb) frame 12
    (kgdb) p *td
    (kgdb) p *td->td_proc

    G> #13 0xffffffff8022c40a in closef (fp=0xffffff009ca95b60, 

    -- 
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
  • Next message: Kövesdán Gábor: "bsdextended mac module question"

    Relevant Pages

    • ddb(4) spoils kernel stack in CURRENT?
      ... My kernel config is: ... kgdb against the resulting kernel dump fails to print complete backtrace: ... Previous frame inner to this frame (corrupt stack?) ...
      (freebsd-current)
    • Kernel panic with IGMPv3
      ... My last running kernel is from 03/05/2009, I can't get a working kernel ... because it panics soon after the boot process (or even while ... Here is the kgdb output with a kernel compiled today from latest ... Previous frame inner to this frame ...
      (freebsd-current)
    • Helping interpreting crash
      ... My FreeBSD server crashed out the other night. ... So could anyone possibly have a look at below (or tell me of somewhere I can go to get the right info..bearing in mind I don't know all that much about the kernel) and let me know what's up? ... kgdb kernel.debug /var/crash/vmcore.1 ... #12 0xc05df0cf in syscall (frame= ...
      (freebsd-questions)
    • Kernel Panic
      ... During the last weeks I am getting sporadic kernel panics. ... I attached the kgdb output and can give additional information when it's ... Previous frame inner to this frame ...
      (freebsd-current)
    • 6.2-STABLE panic in network multicast-address related cleanup code
      ... The following kernel panic occurred twice yesterday evening under ... # kgdb /boot/kernel/kernel.debug vmcore.40 ... #19 0xc06e6577 in syscall (frame= ... Seems like some multi-cast related cleanups are broken. ...
      (freebsd-stable)