From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 16 12:27:52 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB1DE16A4B3; Tue, 16 Sep 2003 12:27:52 -0700 (PDT) Received: from wvths.com (h0009b74df4c5.ne.client2.attbi.com [66.31.200.227]) by mx1.FreeBSD.org (Postfix) with SMTP id B94D343F93; Tue, 16 Sep 2003 12:27:50 -0700 (PDT) (envelope-from sysadmin@wvths.com) Received: from localhost (mail.wvths.com [127.0.0.1]) by wvths.com (WVTHS Mail Gateway) with ESMTP id 8D5A3FD99; Tue, 16 Sep 2003 15:31:53 -0400 (EDT) Received: from wvths.com ([127.0.0.1]) by localhost (mail.wvths.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22675-06; Tue, 16 Sep 2003 15:31:50 -0400 (EDT) Received: from webmail.wvths.com (webmail.wvths.com [192.168.0.6]) by wvths.com (WVTHS Mail Gateway) with SMTP id 80FACFD98; Tue, 16 Sep 2003 15:31:48 -0400 (EDT) Received: from 24.218.220.202 (SquirrelMail authenticated user sysadmin) by webmail.wvths.com with HTTP; Tue, 16 Sep 2003 15:24:56 -0400 (EDT) Message-ID: <24022.24.218.220.202.1063740296.squirrel@webmail.wvths.com> In-Reply-To: <20030916210151.J47434@cvs.imp.ch> References: <20030916105810.U63985@news1.macomnet.ru> <23988.24.218.220.202.1063738362.squirrel@webmail.wvths.com> <20030916210151.J47434@cvs.imp.ch> Date: Tue, 16 Sep 2003 15:24:56 -0400 (EDT) From: sysadmin@wvths.com To: "Martin Blapp" User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal X-Virus-Scanned: by Sophos AntiVirus Engine Content-Transfer-Encoding: quoted-printable cc: sysadmin@wvths.com cc: hackers@freebsd.org cc: mbr@freebsd.org Subject: Re: 4.8-stable kernel panic X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2003 19:27:52 -0000 > > Hi, > >> #0 dumpsys () at ../../kern/kern_shutdown.c:487 >> #1 0xc0168237 in boot (howto=3D256) at ../../kern/kern_shutdown.c:316 >> #2 0xc0168675 in panic (fmt=3D0xc02db260 "m_copydata, offset > size o= f >> mbuf >> chain") at ../../kern/kern_shutdown.c:595 >> #3 0xc018576e in m_copydata (m=3D0xc1560d00, off=3D6144, len=3D2048, >> cp=3D0xc155a800 "") at ../../kern/uipc_mbuf.c:979 >> #4 0xc0186776 in m_defrag (m0=3D0xc1560d00, how=3D1) at >> ../../kern/uipc_mbuf.c:1572 >> #5 0xc021de70 in dc_encap (sc=3D0xc21c3000, m_head=3D0xc1560d00, >> txidx=3D0xd72d9f60) at ../../pci/if_dc.c:3006 >> #6 0xc021e0bb in dc_start (ifp=3D0xc21c3000) at ../../pci/if_dc.c:310= 5 >> #7 0xc021de09 in dc_intr (arg=3D0xc21c3000) at ../../pci/if_dc.c:2970 > > This doesn't help me at all. Looks like corrupted mbufs, this doesn't > have to be in the if_dc driver itself. > > So how can you reproduce this panic, is it a fresh panic at all, or > did you encounter it since ever ? What kind of card do you have (pcicon= f > -lv) ? I remember first being able to get this panic around the beggining of August, maybe earlier. Reproduce it using this shell script: --- #!/bin/bash while :; do ping -f -s 65467 ip_addr & done --- Here's the NIC info: dc0@pci2:9:0: class=3D0x020000 card=3D0x00ed16ec chip=3D0x12161113 rev=3D= 0x11 hdr=3D0x00 vendor =3D 'Accton Technology Corporation' device =3D 'EN5251-Based Fast Ethernet Adapter' class =3D network subclass =3D ethernet HTH,