From owner-freebsd-bugs Wed Aug 25 9:11:42 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 3258815135 for ; Wed, 25 Aug 1999 09:11:41 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id JAA05195; Wed, 25 Aug 1999 09:10:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from quack.kfu.com (quack.kfu.com [170.1.70.2]) by hub.freebsd.org (Postfix) with ESMTP id 290151598E for ; Wed, 25 Aug 1999 09:01:00 -0700 (PDT) (envelope-from nsayer@medusa.kfu.com) Received: from medusa.kfu.com (medusa.kfu.com [170.1.70.5]) by quack.kfu.com (8.9.2/8.8.5) with ESMTP id JAA78604 for ; Wed, 25 Aug 1999 09:00:28 -0700 (PDT) Received: (from nsayer@localhost) by medusa.kfu.com (8.9.2/8.8.8) id JAA17794; Wed, 25 Aug 1999 09:00:27 -0700 (PDT) (envelope-from nsayer) Message-Id: <199908251600.JAA17794@medusa.kfu.com> Date: Wed, 25 Aug 1999 09:00:27 -0700 (PDT) From: nsayer@freebsd.org Reply-To: nsayer@freebsd.org To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/13377: if_tx: 83c170 chip revision 0x07 causes lockup? Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 13377 >Category: kern >Synopsis: if_tx: 83c170 chip revision 0x07 causes lockup? >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Aug 25 09:10:00 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Nick Sayer >Release: FreeBSD 3.2-RELEASE i386 >Organization: Just me >Environment: Two more or less identical machines doing bridging with pairs of tx cards. >Description: One machine has a pair of rev 0x06 cards. One has a 0x06 and a 0x07 card. The machine with the 0x07 card has to be rebooted every couple of days. The 0x07 interface basically just goes dead. I will swap out the 0x07 with a 0x06 to see if it goes away, but I bet it will. >How-To-Repeat: It is unclear whether turning on promiscuous mode (which is what bridging does) brings out this bug or not. It may even be a hardware bug, but if it is across rev 0x07 chips, then it will at least need to be worked around. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message