From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx1.redhat.com ([209.132.183.28]:38708 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753561AbcHXI1j (ORCPT ); Wed, 24 Aug 2016 04:27:39 -0400 Date: Wed, 24 Aug 2016 16:27:36 +0800 From: Eryu Guan Subject: Re: [sparc64] ext4 TPC and call trace (process blocked/stuck) on git kernel 4.8.0-rc3+ Message-ID: <20160824082736.GQ27776@eguan.usersys.redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: fstests-owner@vger.kernel.org To: Anatoly Pugachev Cc: linux-ext4@vger.kernel.org, sparclinux@vger.kernel.org, fstests@vger.kernel.org List-ID: On Wed, Aug 24, 2016 at 11:13:25AM +0300, Anatoly Pugachev wrote: > Hello! > > Running fstests (xfstests) suite on sparc64 debian sid/unstable with > linux kernel 4.8.0-rc3+ , I'm getting the following call trace and TPC > on server console and system logs: > > mator@nvg5120:~/xfstests-dev$ ./check ext4/022 ext4/022 is known to hang, and AFAIK the fixes are pending on review and not merged to mainline kernel yet. Please see this patchset https://www.spinics.net/lists/linux-ext4/msg53200.html And ext4/022 is in dangerous group, I think you can skip it by adding "-x dangerous" to your check options (skip all tests in dangerous group), e.g. ./check -g auto -x dangerous Thanks, Eryu