From owner-freebsd-net@FreeBSD.ORG Sat May 24 07:35:27 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E753C1065675 for ; Sat, 24 May 2008 07:35:27 +0000 (UTC) (envelope-from neil@hoggarth.me.uk) Received: from neilhoggarth-2.dsl.easynet.co.uk (neilhoggarth-2.dsl.easynet.co.uk [217.206.124.94]) by mx1.freebsd.org (Postfix) with ESMTP id 805418FC17 for ; Sat, 24 May 2008 07:35:27 +0000 (UTC) (envelope-from neil@hoggarth.me.uk) Received: from neilhoggarth-2.dsl.easynet.co.uk (localhost [127.0.0.1]) by neilhoggarth-2.dsl.easynet.co.uk (8.14.2/8.14.2) with ESMTP id m4O7ZOCf001032; Sat, 24 May 2008 08:35:24 +0100 (BST) (envelope-from neil@hoggarth.me.uk) Received: from localhost (njh@localhost) by neilhoggarth-2.dsl.easynet.co.uk (8.14.2/8.14.2/Submit) with ESMTP id m4O7ZMKT001029; Sat, 24 May 2008 08:35:24 +0100 (BST) (envelope-from neil@hoggarth.me.uk) X-Authentication-Warning: neilhoggarth-2.dsl.easynet.co.uk: njh owned process doing -bs Date: Sat, 24 May 2008 08:35:22 +0100 (BST) From: Neil Hoggarth X-X-Sender: njh@neilhoggarth-2.dsl.easynet.co.uk To: Jack Vogel In-Reply-To: <2a41acea0805211352s37e6fd40maaaac90e51912947@mail.gmail.com> Message-ID: References: <2a41acea0805211326v74baa017tc03fcd329a764ef5@mail.gmail.com> <2a41acea0805211352s37e6fd40maaaac90e51912947@mail.gmail.com> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: [em][panic] recursed on non-recursive mutex em0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 May 2008 07:35:28 -0000 On Wed, 21 May 2008, Jack Vogel wrote: >>> I opened PR kern/122928 last month, describing my problems with Intel > > OPPS, I think I found the problem, look for a delta on if_em.c shortly. > > Let me know if this fixes your problem. Thanks. I picked up delta 1.184.2.3 to if_em.c on Thursday morning. The system no longer panics on watchdog timeout, but the original problem from PR kern/122928 remains - once a watchdog timeout occurs the interface no longer seems to receive packets and never properly recovers, short of rebooting the system (or perhaps the watchdog timeout is actually a symptom of whatever has "got stuck", rather than a cause?). The PR is still in "feedback" state, but I think I've provided the requested information. Is there anything else that I can do to help progress this? Regards, Neil.