Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 4 Sep 1999 16:41:12 -0500
From:      Paul Saab <paul@mu.org>
To:        stable@freebsd.org
Subject:   analyzing a crash of 3.2-RELEASE
Message-ID:  <19990904164112.A47315@elvis.mu.org>

next in thread | raw e-mail | index | archive | help
I have been trying to figure out why exactly this panic is occurring
and I am stumped.  The scenero is like this:

We currently have 40 machines to serve up small graphics for our
web site and we are currently evaluating other solutions to retire
the current architecture, and one of them is NT.  I for one do not
want to let NT onto the site, so I build a 3.2-RELEASE machine
running thttpd to replace all 40 servers, and not surprisingly,
the machine was able to handle the entire load.  Lets just say this
pissed off our NT people a lot and has scared them, because this
was their attempt to get it onto the site.

Now onto the problem..  After about an hour or so in production
(20-30 minutes if running in dual-proc) the machine panics with
"free: multiple free".  Below is the backtrace.  If someone can
help me out, or point me in the right direction I'd appreciate it.
This is really the only thing stopping us from putting it into
production across the site.  I also looked at the commit logs and
mailing lists and I could not find if this problem has already been
fixed.

If you are not familiar with the way thttpd works, it is basically
a single threaded web server that runs in a big select loop,
accepting as many connections as possible and then spiting out the
data to the client as quickly as possible.  On our site we are
handling between 500-1000 connections/second with the CPU load at
about 80-85%.

(kgdb) bt
#0  boot (howto=256) at ../../kern/kern_shutdown.c:285
#1  0xc015bab9 in panic (fmt=0xc020f3a3 "free: multiple frees")
    at ../../kern/kern_shutdown.c:446
#2  0xc0158863 in free (addr=0xc40b6600, type=0xc024f270)
    at ../../kern/kern_malloc.c:333
#3  0xc01955d2 in ifafree (ifa=0xc40b6600) at ../../net/route.c:262
#4  0xc0195556 in rtfree (rt=0xc4ea9d00) at ../../net/route.c:236
#5  0xc0195960 in rtrequest (req=2, dst=0xc4ea8de0, gateway=0xc4ea8df0, 
    netmask=0x0, flags=393223, ret_nrt=0x0) at ../../net/route.c:536
#6  0xc019a031 in in_rtqkill (rn=0xc4ea9d00, rock=0xcd7d2f74)
    at ../../netinet/in_rmx.c:242
#7  0xc0194d64 in rn_walktree (h=0xc409b080, f=0xc0199fe0 <in_rtqkill>, 
    w=0xcd7d2f74) at ../../net/radix.c:956
#8  0xc019a0de in in_rtqtimo (rock=0xc409b080) at ../../netinet/in_rmx.c:283
#9  0xc015fea3 in softclock () at ../../kern/kern_timeout.c:124
#10 0xc01db813 in doreti_swi ()
#11 0x8049761 in ?? ()

paul


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990904164112.A47315>