Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 13 Aug 1996 08:45:06 +0200 (MET DST)
From:      J Wunsch <j@uriah.heep.sax.de>
To:        freebsd-hackers@freebsd.org (FreeBSD hackers)
Cc:        lmcsato@lmc.ericsson.se (Samy Touati)
Subject:   Re: machine crashing, what panic: free means?
Message-ID:  <199608130645.IAA03159@uriah.heep.sax.de>
In-Reply-To: <Pine.Sola.3.91.960812223736.6012A-100000@chicago> from Samy Touati at "Aug 12, 96 10:41:26 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
As Samy Touati wrote:

> #0  boot (howto=256) at ../../i386/i386/machdep.c:892
> #1  0xf0112a73 in panic (fmt=0xf010baa2 "free: multiple frees")
>     at ../../kern/subr_prf.c:124
> #2  0xf010bb83 in free (addr=0xf05c4b80, type=1)
>     at ../../kern/kern_malloc.c:337 
> #3  0xf0138aca in pppstart (tp=0xf01b52e8) at ../../net/if_ppp.c:1042
> #4  0xf019ed7b in siopoll () at ../../i386/isa/sio.c:1554
> #5  0xf0187067 in doreti_swi ()
> #6  0xf018f25c in cpu_switch ()
> 
> 
> After browsing through the sources, it seems that the problem is related 
> to the sio port being saturated.

No, your conclusion is wrong.  It's rather that the code on line 1042
in sys/net/if_ppp.c has called a free() which was a duplicate free.
This should not happen, regardless of whether the port is saturated or
not.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)



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