Date: Thu, 25 Jul 2013 09:56:59 +0200 From: Dominic Fandrey <kamikaze@bsdforen.de> To: Konstantin Belousov <kostikbel@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: stopping amd causes a freeze Message-ID: <51F0DA4B.3000809@bsdforen.de> In-Reply-To: <20130722100720.GI5991@kib.kiev.ua> References: <51ED0060.2050502@bsdforen.de> <20130722100720.GI5991@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22/07/2013 12:07, Konstantin Belousov wrote: > On Mon, Jul 22, 2013 at 11:50:24AM +0200, Dominic Fandrey wrote: >> ... >> >> 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- SIGTERM may cause the freeze. >> >> Nothing was mounted (by amd) during the last freeze. >> >> ... > > Are you sure that the machine did not paniced ? Do you have serial console ? > > 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. I tried that. Applying the diff was straightforward enough. But the resulting kernel paniced as soon as it tried to mount the root fs. So I'll wait for the MFC from someone who knows what he/she is doing. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51F0DA4B.3000809>