Date: Tue, 23 Jul 2013 19:43:00 +0200 From: Dominic Fandrey <kamikaze@bsdforen.de> To: Artem Belevich <art@freebsd.org> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: stopping amd causes a freeze Message-ID: <51EEC0A4.7010508@bsdforen.de> In-Reply-To: <CAFqOu6jkH0yWnWddGwZktLmBzGGHpurkEaeiqN11ArHjmW8q_w@mail.gmail.com> References: <51ED0060.2050502@bsdforen.de> <CAFqOu6jkH0yWnWddGwZktLmBzGGHpurkEaeiqN11ArHjmW8q_w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22/07/2013 20:05, Artem Belevich wrote: > On Mon, Jul 22, 2013 at 2:50 AM, Dominic Fandrey <kamikaze@bsdforen.de>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. >> > > Don't use KILL or make sure that nobody tries to use amd mountpoints until > new instance starts. Manually unmounting them before killing amd may help. > Why not let amd do it itself with "/etc/rc.d/amd stop" ? That was a typo, I'm using SIGTERM. Sorry about that. -- 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?51EEC0A4.7010508>