From owner-freebsd-current Mon Jul 13 10:29:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00765 for freebsd-current-outgoing; Mon, 13 Jul 1998 10:29:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00759 for ; Mon, 13 Jul 1998 10:29:10 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id MAA22835; Mon, 13 Jul 1998 12:28:56 -0500 (CDT) From: Kevin Day Message-Id: <199807131728.MAA22835@home.dragondata.com> Subject: Re: panic in the dec driver In-Reply-To: <199807131712.LAA03753@panzer.plutotech.com> from "Kenneth D. Merry" at "Jul 13, 98 11:12:38 am" To: ken@plutotech.com (Kenneth D. Merry) Date: Mon, 13 Jul 1998 12:28:56 -0500 (CDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I got a panic today in the DEC driver, and I was wondering if > anyone has seen anything similar. Here's a stack trace: > > ======================================================================== > tulip_txput (sc=0xf08b5800, m=0xf0538f00) at machine/pmap.h:172 > (kgdb) where > #0 tulip_txput (sc=0xf08b5800, m=0xf0538f00) at machine/pmap.h:172 > #1 0xf01cb4ad in tulip_ifstart_one (ifp=0xf08b5818) at ../../pci/if_de.c:4843 > #2 0xf017965c in ether_output (ifp=0xf08b5818, m0=0xf0536000, dst=0xf336cb70, > rt0=0xf08e7f00) at ../../net/if_ethersubr.c:385 > #3 0xf018b6f8 in ip_output (m0=0xf0536000, opt=0x0, ro=0xf336cb6c, flags=0, Yep, I've seen the same thing, about once a month.... Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message