From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 16 11:55:36 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 CAEBA16A4BF; Tue, 16 Sep 2003 11:55:36 -0700 (PDT) Received: from wvths.com (h0009b74df4c5.ne.client2.attbi.com [66.31.200.227]) by mx1.FreeBSD.org (Postfix) with SMTP id 11E7243FA3; Tue, 16 Sep 2003 11:55:35 -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 B9A3EFD9B; Tue, 16 Sep 2003 14:59:37 -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 22686-01; Tue, 16 Sep 2003 14:59:34 -0400 (EDT) Received: from webmail.wvths.com (www.wvths.com [192.168.0.6]) by wvths.com (WVTHS Mail Gateway) with SMTP id E0101FD9A; Tue, 16 Sep 2003 14:59:33 -0400 (EDT) Received: from 24.218.220.202 (SquirrelMail authenticated user sysadmin) by webmail.wvths.com with HTTP; Tue, 16 Sep 2003 14:52:42 -0400 (EDT) Message-ID: <23988.24.218.220.202.1063738362.squirrel@webmail.wvths.com> In-Reply-To: <20030916105810.U63985@news1.macomnet.ru> References: <20030916105810.U63985@news1.macomnet.ru> Date: Tue, 16 Sep 2003 14:52:42 -0400 (EDT) From: sysadmin@wvths.com To: hackers@freebsd.org 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: 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 18:55:36 -0000 > Do you use any klds? What does kldstat say? No klds loaded. Well, it looks like the dc net driver is causing the panic. After some testing, I got this backtrace: --- #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 of m= buf 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:3105 #7 0xc021de09 in dc_intr (arg=3D0xc21c3000) at ../../pci/if_dc.c:2970 #8 0xc02b419d in intr_mux (arg=3D0xc144e3a0) at ../../i386/isa/intr_machdep.c:601 #9 0x8068e79 in ?? () #10 0x8061e3c in ?? () #11 0x8063c75 in ?? () #12 0x8061c2a in ?? () #13 0x8060047 in ?? () #14 0x805ffeb in ?? () #15 0x805e3f5 in ?? () #16 0x8048e29 in ?? () #17 0x804813e in ?? () (kgdb) up 3 #3 0xc018576e in m_copydata (m=3D0xc1560d00, off=3D6144, len=3D2048, cp=3D0xc155a800 "") at ../../kern/uipc_mbuf.c:979 979 KASSERT(m !=3D NULL, ("m_copydata, offset > size = of mbuf chain")); (kgdb) up #4 0xc0186776 in m_defrag (m0=3D0xc1560d00, how=3D1) at ../../kern/uipc_mbuf.c:1572 1572 m_copydata(m0, progress, length, mtod(m_new, caddr_t)); (kgdb) up #5 0xc021de70 in dc_encap (sc=3D0xc21c3000, m_head=3D0xc1560d00, txidx=3D0xd72d9f60) at ../../pci/if_dc.c:3006 3006 m =3D m_defrag(m_head, M_DONTWAIT); (kgdb) up #6 0xc021e0bb in dc_start (ifp=3D0xc21c3000) at ../../pci/if_dc.c:3105 3105 if (dc_encap(sc, m_head, &idx)) { (kgdb) up #7 0xc021de09 in dc_intr (arg=3D0xc21c3000) at ../../pci/if_dc.c:2970 2970 dc_start(ifp); (kgdb) up #8 0xc02b419d in intr_mux (arg=3D0xc144e3a0) at ../../i386/isa/intr_machdep.c:601 601 p->handler(p->argument); --- After switching to the xl-based NIC, I couldn't reproduce the crash anymo= re. Thanks,