From owner-freebsd-stable@FreeBSD.ORG Mon Jul 22 12:35:50 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AE7408BC for ; Mon, 22 Jul 2013 12:35:50 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 715762B71 for ; Mon, 22 Jul 2013 12:35:50 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1V1FL3-0000Ab-Eu; Mon, 22 Jul 2013 14:35:41 +0200 Received: from [81.21.138.17] (helo=ronaldradial.versatec.local) by smtp.greenhost.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1V1FL3-00064T-RE; Mon, 22 Jul 2013 14:35:41 +0200 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: "Konstantin Belousov" , "Dominic Fandrey" Subject: Re: stopping amd causes a freeze References: <51ED0060.2050502@bsdforen.de> <20130722100720.GI5991@kib.kiev.ua> <51ED2360.2060104@bsdforen.de> Date: Mon, 22 Jul 2013 14:35:37 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Ronald Klop" Message-ID: In-Reply-To: <51ED2360.2060104@bsdforen.de> User-Agent: Opera Mail/12.16 (Win32) X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: 0.8 X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50 autolearn=disabled version=3.3.1 X-Scan-Signature: ba572e8a3bde05b4b19613c12a9e49fc Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jul 2013 12:35:50 -0000 On Mon, 22 Jul 2013 14:19:44 +0200, Dominic Fandrey wrote: > On 22/07/2013 12:07, Konstantin Belousov wrote: >> On Mon, Jul 22, 2013 at 11:50:24AM +0200, Dominic Fandrey wrote: >>> Occasionally stopping amd freezes my system. It's a rare occurrence, >>> and I haven't found a reliable way to reproduce it. >>> >>> It's also a real freeze, so there's no way to get into the debugger >>> or grab a core dump. I only can perform the 4 seconds hard shutdown to >>> revive the system. >>> >>> I run amd through sysutils/automounter, which is a scripting solution >>> that generates an amd.map file based on encountered devices and devd >>> events. The SIGHUP it sends to amd to tell it the map file was updated >>> does not cause problems, only a SIGKILL may cause the freeze. >>> >>> Nothing was mounted (by amd) during the last freeze. >>> >>> I don't see any angle to tackle this, but I'm throwing it out here >>> any way, in the hopes that someone actually has an idea how to approach >>> the issue. >> >> Are you sure that the machine did not paniced ? Do you have serial >> console ? > > No, I don't have one. All that I can tell is that everything freezes > (i.e. Xorg screen and mouse). ACPI events like shutdown don't cause a > reaction. And the system doesn't respond to ICMP queries. > >> The amd(8) locks itself into memory, most likely due to the fear of >> deadlock. There are some known issues with user wirings in stable/9. >> If the problem you see is indeed due to wiring, you might try to apply >> r253187-r253191. > > From head? That may be worth a try. It would be better for testing if I > managed to reproduce the problem reliably, before I test patches. > > I see it's scheduled for MFC, soon. > Did you try a run with the INVARIANTS, etc. options in the kernel? That enables more sanity checking for locks which is too slow for production. Ronald.