From owner-freebsd-hackers@freebsd.org  Wed Aug  9 08:46:06 2017
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB803DC6E3B
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Wed,  9 Aug 2017 08:46:06 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2772C6870F
 for <freebsd-hackers@freebsd.org>; Wed,  9 Aug 2017 08:46:05 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from tom.home (kib@localhost [127.0.0.1])
 by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v798jksC023294
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Wed, 9 Aug 2017 11:45:46 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v798jksC023294
Received: (from kostik@localhost)
 by tom.home (8.15.2/8.15.2/Submit) id v798jkqw023293;
 Wed, 9 Aug 2017 11:45:46 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com
 using -f
Date: Wed, 9 Aug 2017 11:45:46 +0300
From: Konstantin Belousov <kostikbel@gmail.com>
To: Gautam <list@execve.net>
Cc: freebsd-hackers@freebsd.org
Subject: Re: Freebsd 11.0 - system freeze on intensive I/O
Message-ID: <20170809084546.GQ1700@kib.kiev.ua>
References: <CAD9pFYAAy8jKcABNTun-Y3knrbUreQ7q1-CCj=323HgLMC5e6g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAD9pFYAAy8jKcABNTun-Y3knrbUreQ7q1-CCj=323HgLMC5e6g@mail.gmail.com>
User-Agent: Mutt/1.8.3 (2017-05-23)
X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00,
 DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no
 autolearn_force=no version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Aug 2017 08:46:06 -0000

On Wed, Aug 09, 2017 at 12:41:02PM +0530, Gautam wrote:
> Hi,
> 
> I raised this topic on freebsd-questions where I suspect a bug caused due
> to swapfile usage on FreeBSD.
> 
> You could read details in the below thread, but summary is that with using
> a swapfile (not a swap partition) the system freezes on some single process
> intensive I/O. This is 100% reproducible.
Also this is expected.

> 
> http://marc.info/?l=freebsd-questions&m=150088763825675&w=2
> 
> I raised a PR - 220971 ; but there are no backtraces / logs etc. that could
> possibly help.
See
https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html

> 
> I would like to help narrow this down, but do not know how. Any suggestions
> on how to debug a system freeze and what I need to do ? I could then try to
> reproduce this and collect the needed information - traces etc.
> 
> Thanks,
> Gautam
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"