From owner-freebsd-bugs@FreeBSD.ORG Fri May 14 05:50:34 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A914816A4D7 for ; Fri, 14 May 2004 05:50:34 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F0D243D31 for ; Fri, 14 May 2004 05:50:34 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i4ECoT59092242 for ; Fri, 14 May 2004 05:50:29 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i4ECoTsE092241; Fri, 14 May 2004 05:50:29 -0700 (PDT) (envelope-from gnats) Resent-Date: Fri, 14 May 2004 05:50:29 -0700 (PDT) Resent-Message-Id: <200405141250.i4ECoTsE092241@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Fabien THOMAS Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E89716A4CE for ; Fri, 14 May 2004 05:45:14 -0700 (PDT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 052E343D41 for ; Fri, 14 May 2004 05:45:14 -0700 (PDT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i4ECjDXl053183 for ; Fri, 14 May 2004 05:45:13 -0700 (PDT) (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.11/8.12.11/Submit) id i4ECjDKK053182; Fri, 14 May 2004 05:45:13 -0700 (PDT) (envelope-from nobody) Message-Id: <200405141245.i4ECjDKK053182@www.freebsd.org> Date: Fri, 14 May 2004 05:45:13 -0700 (PDT) From: Fabien THOMAS To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: kern/66634: hard lock with em driver X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 May 2004 12:50:34 -0000 >Number: 66634 >Category: kern >Synopsis: hard lock with em driver >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri May 14 05:50:29 PDT 2004 >Closed-Date: >Last-Modified: >Originator: Fabien THOMAS >Release: 4.9 >Organization: NETASQ >Environment: FreeBSD build-current 4.9-RELEASE-p2 FreeBSD 4.9-RELEASE-p2 #0: Mon Mar 1 10:22:36 CET 2004 root@build-current:/usr/src/sys/compile/GENERIC i386 >Description: We use a lot of intel gigabit card and since the first time we use it we experience some strange hard lock of the system (4.9|FreeBSD-stable). We have tried several driver version (it is not related to a version). We use the card in polling mode but it seems that the problem can be fired even in interrupt mode. What i found during the debugging on a fiber card: 1) original driver did not lock but when the other end is rebooted i've around 10 linkup/linkdown 2) removing linkup/linkdown printf: driver lock each time the other end system is rebooted! 3) removing the E1000_IMC_RXSEQ in disable_intr correct the lock but i do not understand why: a) E1000_IMC_RXSEQ need to be left when disabling intr? b) the system completly lock (even under debugger) for just an interrupt source enabled? static void em_disable_intr(struct adapter *adapter) { E1000_WRITE_REG(&adapter->hw, IMC, (0xffffffff));/* & ~E1000_IMC_RXSEQ));*/ return; } >How-To-Repeat: use an intel dual port fiber card based on 546 chip for example remove driver printf for linkup/linkdown reboot the other end >Fix: >Release-Note: >Audit-Trail: >Unformatted: