From owner-freebsd-bugs Mon Feb 12 18:10: 6 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3BC5537B491 for ; Mon, 12 Feb 2001 18:10:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f1D2A3A92024; Mon, 12 Feb 2001 18:10:03 -0800 (PST) (envelope-from gnats) Date: Mon, 12 Feb 2001 18:10:03 -0800 (PST) Message-Id: <200102130210.f1D2A3A92024@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: howard@ee.elen.utah.edu (Walt Howard) Subject: Re: kern/24978: "dc" network interface goes into continuous reset Reply-To: howard@ee.elen.utah.edu (Walt Howard) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24978; it has been noted by GNATS. From: howard@ee.utah.edu (Walt Howard) To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: kern/24978: "dc" network interface goes into continuous reset Date: Mon, 12 Feb 2001 19:08:55 -0700 (MST) This may be a bogus report. The computer showed a major hardware fault when rebooted (kernel panic - trap 12 - failure to page in) and the problem with the dc0 interface might very well be an indication that the driver is doing just what it should - reacting gracefully to an out-of-the-ordinary condition. I couldn't let you know sooner since the machine with the problem is our mail relay.... Sorry for the probable false alarm. >>Walt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message