From owner-freebsd-net@FreeBSD.ORG Wed Sep 7 23:57:18 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A0FA106564A for ; Wed, 7 Sep 2011 23:57:18 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-vw0-f50.google.com (mail-vw0-f50.google.com [209.85.212.50]) by mx1.freebsd.org (Postfix) with ESMTP id 419AA8FC0A for ; Wed, 7 Sep 2011 23:57:17 +0000 (UTC) Received: by vws14 with SMTP id 14so317778vws.37 for ; Wed, 07 Sep 2011 16:57:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4JnmgbJMz0tBWzZ3uzHdIou9LlbxpqeSgZbEwJNugvg=; b=NJytfQi0YaS0aGUIlZE71g6kR4ytiY6kMFl7kZdPEd1bZY1gPz01pTY9lFvzxmb/OW u1aueYksKEwQ5pa3oXMeyff9byax1MVVT1Ia3WN/nROXwcNl1kThEcyMT1WPuu7FBtG8 gAqh0I16X0RJSJA25gib0VkLjAknvmYj+JxoU= MIME-Version: 1.0 Received: by 10.52.91.34 with SMTP id cb2mr21455vdb.244.1315439837439; Wed, 07 Sep 2011 16:57:17 -0700 (PDT) Received: by 10.52.160.170 with HTTP; Wed, 7 Sep 2011 16:57:17 -0700 (PDT) In-Reply-To: References: Date: Wed, 7 Sep 2011 16:57:17 -0700 Message-ID: From: Jack Vogel To: Arnaud Lacombe Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: FreeBSD 7-STABLE mbuf corruption X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 23:57:18 -0000 I have seen this, but I don't have any hot ideas right off the top of my head yet :( Jack On Wed, Sep 7, 2011 at 4:19 PM, Arnaud Lacombe wrote: > Hi, > > On Mon, Sep 5, 2011 at 2:59 AM, Arnaud Lacombe wrote: > > Hi folks, > > > > We have been trying to track down a bad mbuf management for about two > > weeks on a customized 7.1 base. I have finally been able to reproduce > > it with a stock FreeBSD 7-STABLE (kernel from r225276, userland from > > 7.4). > > > > With the help of the attached patches, I have just been able to > > trigger the following panic: > > > > panic: Corrupted unused flags, expected 0xffffffff00000000, got 0x0, > flags 0x3 > > cpuid = 1 > > Uptime: 3d10h5m3s > > Cannot dump. No dump device defined > > > General form of the crash is: > > panic: Corrupted unused flags, expected 0xffffffff00000000, got > 0xbabe0000000000, flags 0xbabe0000babe00 > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper(c0874e29,0,c0835757,f4574c48,0,...) at > db_trace_self_wrapper+0x26 > panic(c0835757,0,ffffffff,0,babe00,...) at panic+0x10b > igb_txeof(c6a25008,0,c0837083,5ea,17c,...) at igb_txeof+0x399 > igb_msix_que(c6a2b800,0,c084d367,4b6,c69dd068,...) at igb_msix_que+0x7b > ithread_loop(c6a29090,f4574d38,c084d0db,31c,c6a16828,...) at > ithread_loop+0xc3 > fork_exit(c061d520,c6a29090,f4574d38) at fork_exit+0xa6 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0, eip = 0, esp = 0xf4574d70, ebp = 0 --- > Uptime: 1m42s > > It happens particularly easily when the box receives wall of SYN > (about 1000 cnx attempts at once) every 5s or so. > > - Arnaud > > > > > [cut stuff no one cares about...] >