From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 16 19:19:16 2005 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4528316A41F; Tue, 16 Aug 2005 19:19:16 +0000 (GMT) (envelope-from sobomax@portaone.com) Received: from www.portaone.com (web.portaone.com [195.70.151.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43CF443D5D; Tue, 16 Aug 2005 19:19:13 +0000 (GMT) (envelope-from sobomax@portaone.com) Received: from [192.168.0.49] (lesnik.portaone.com [195.140.246.50] (may be forged)) (authenticated bits=0) by www.portaone.com (8.12.11/8.12.11) with ESMTP id j7GIoea1006057 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Aug 2005 20:50:41 +0200 (CEST) (envelope-from sobomax@portaone.com) Message-ID: <43023577.6080108@portaone.com> Date: Tue, 16 Aug 2005 21:50:31 +0300 From: Maxim Sobolev Organization: Porta Software Ltd User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@FreeBSD.org, bms@FreeBSD.org, drosih@rpi.edu, Bill Paul , John Baldwin , Alexander Timoshenko , bug-followup@FreeBSD.org, Alexander Timoshenko Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.86.2/1023/Mon Aug 15 22:15:08 2005 on www.portaone.com X-Virus-Status: Clean X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.0 X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on www.portaone.com X-Mailman-Approved-At: Wed, 17 Aug 2005 11:52:53 +0000 Cc: Subject: Network interrupt after shutdown method has been called [kern/62889] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Maxim.Sobolev@portaone.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Aug 2005 19:19:16 -0000 Folks, We experience a 100% reproducible panic on one of our machines during shutdown+power off. We have found that it's caused by the interrupt which happens in re(4) after re_shutdown() method has been called. Quick googling reveals that we are not alone who experience this problem and such condition sometimes happens as a result of interaction with the particular ACPI implementation on shutdown+power off. Some FreeBSD network drivers have been patched to workaround for the problem (i.e. vr(4), see kern/62889), but quick browsing through sources suggests that majority still can be affected by the exactly the same problem. Hence the question: Who is "guilty"? Can the network driver make an assumption that no interrupt will happen after its foo_shutdown() has been called? Or such assumption cannot be made? In the former case most of the network drivers have to be fixed (usually by turning foo_shutdown() into a wrapper to foo_detach() as with vr(4)), while in the latter the reason of this stray irq should be investigated further and fixed where appropriate. Any comments/ideas? -Maxim