From owner-freebsd-questions  Mon Dec 15 08:43:03 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id IAA11921
          for questions-outgoing; Mon, 15 Dec 1997 08:43:03 -0800 (PST)
          (envelope-from owner-freebsd-questions)
Received: from mojo.calyx.net (mojo.calyx.net [208.132.136.2])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA11903
          for <freebsd-questions@freebsd.org>; Mon, 15 Dec 1997 08:42:57 -0800 (PST)
          (envelope-from lists@mojo.calyx.net)
Message-Id: <199712151642.IAA11903@hub.freebsd.org>
Received: (qmail 23143 invoked from network); 15 Dec 1997 16:42:54 -0000
Received: from kwesi.calyx.net (208.132.136.100)
  by mojo.calyx.net with SMTP; 15 Dec 1997 16:42:54 -0000
X-Sender: lists@calyx.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Release Candidate 3
Date: Sun, 14 Dec 1997 11:42:46 -0500
To: freebsd-questions@freebsd.org
From: Nicholas Merrill <lists@mojo.calyx.net>
Subject: Re: de0: abnormal interrupt: transmit underflow: SOLVED(?)
In-Reply-To: <199712142252.OAA18257@hub.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

At 05:52 PM 12/13/97 -0500, you wrote:
>Hi.. I recently upgraded my motherboard from an ASUS
>P55T2P4 to the P/I-XP6NP5 Pentium Pro board, with a
>200Mhz PPro CPU (256k cache).
>
>I am having this trouble with my Accton dec21040 ethernet
>board in that it keeps generating this error:
>
>Dec 14 17:33:16 mojo /kernel: de0: abnormal interrupt: transmit underflow
>Dec 14 17:42:13 mojo /kernel: de0: abnormal interrupt: transmit underflow
>Dec 14 17:42:47 mojo /kernel: de0: abnormal interrupt: transmit underflow
>
>I was just wondering if anybody has seen this, and what it might mean?
>These are steps I've already taken:
>
>- Switching the PCI slots of the Buslogic card and the ether.
>- Resetting the BIOS to default settings, and then re-starting

After that, I upgraded the BIOS on my motherboard to the newest revision
that was posted on the ASUS website and the problem appears to have
disappeared.

Something to consider if anyone else finds this error in the future.

Regards

Nick