From owner-freebsd-questions Fri Dec 10 21:39:32 1999 Delivered-To: freebsd-questions@freebsd.org Received: from brix.vintners.net (uswest-dsl-136-17.cortland.com [209.162.136.17]) by hub.freebsd.org (Postfix) with ESMTP id 27D5514F8E for ; Fri, 10 Dec 1999 21:39:25 -0800 (PST) (envelope-from mikel@vintners.net) Received: from brix.vintners.net (brix.vintners.net [209.162.136.17]) by brix.vintners.net (8.9.3/8.9.3) with ESMTP id VAA44661 for ; Fri, 10 Dec 1999 21:39:05 -0800 (PST) (envelope-from mikel@vintners.net) Date: Fri, 10 Dec 1999 21:39:04 -0800 (PST) Message-Id: <199912110539.VAA44661@brix.vintners.net> To: freebsd-questions@freebsd.org Subject: transmit underflow? From: mikel@vintners.net (Mike Lempriere) Reply-To: mikel@vintners.net (Mike Lempriere) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Excerpt from a freebsd nightly security check output: > > de0: abnormal interrupt: transmit underflow (raising TX threshold to > 160|1024) There's several lines like this with both numbers getting bigger. It seems to go through this again a day or two after any reboot. The message wording makes it sound like it's taking care of the problem, whatever it really is... a) Is this a problem (something I need to worry about)? b) Is there something I can do to set it up right at boot time instead of it's renegotiating it's way up over the next few days? (By the way, if it helps any, it's a DEC Pentium 266 with a DE450 and a DE500 NIC, the latter is having the problem. It's running RELEASE-3.3.) Thanks! -- Pacific NorthWest wine, blues, jazz info; http://vintners.net/~mikel Mike Lempriere: mikel@vintners.net; work: MLempriere@ActiveVoice.com WA State resident-junk email prohibited by law: RCW19.190 & RCW19.86 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message