Date: Thu, 12 Sep 2013 09:45:48 +0200 (CEST) From: Jimmy Olgeni <olgeni@olgeni.com> To: Konstantin Belousov <kostikbel@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: Possible kqueue related issue on STABLE/RC. Message-ID: <alpine.BSF.2.00.1309120942240.51816@localhost.my.domain> In-Reply-To: <20130912073643.GM41229@kib.kiev.ua> References: <alpine.BSF.2.00.1309111705460.89324@olgeni.olgeni> <20130911171913.GG41229@kib.kiev.ua> <alpine.BSF.2.00.1309112316160.2547@olgeni.olgeni> <20130912073643.GM41229@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 12 Sep 2013, Konstantin Belousov wrote: >> This time I tried with clang + these options and I got something more >> interesting. All works fine until the lock violation below: > Clang is, well, not relevant there. Still, with clang I could get a hard reset rather than a hang. But maybe there are two different issues. I'll run more tests and see if the fifo problem goes away with your patch below. > It seems you edited the kernel output, at least rearranging large blocks > of text. I tried to interpret what I see in a useful way. I got the message buffer from a minidump, here: http://olgeni.olgeni.com/~olgeni/textdump.tar.1 > Might be, your issue is that some filesystems do not care about proper > locking mode for the fifos. UFS carefully disables shared locking for > VFIFO, but it seems ZFS is not. I can propose the following band-aid, > which could help you. Thanks a lot! I'll give it a run when I get back home. -- jimmy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1309120942240.51816>