Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753955AbaJGPKo (ORCPT ); Tue, 7 Oct 2014 11:10:44 -0400 Received: from g4t3427.houston.hp.com ([15.201.208.55]:10067 "EHLO g4t3427.houston.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752281AbaJGPKl (ORCPT ); Tue, 7 Oct 2014 11:10:41 -0400 Message-ID: <5434026F.3070404@hp.com> Date: Tue, 07 Oct 2014 11:10:39 -0400 From: Waiman Long User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130109 Thunderbird/10.0.12 MIME-Version: 1.0 To: Chuck Ebbert CC: Fengguang Wu , Dave Hansen , Ingo Molnar , LKML , lkp@01.org, "linux-btrfs@vger.kernel.org" , Chris Mason Subject: Re: [x86, locking/rwlocks, btrfs] INFO: rcu_sched self-detected stall on CPU References: <20141003133351.GC32634@wfg-t540p.sh.intel.com> <542F693E.5070200@hp.com> <20141004050628.4613752a@as> In-Reply-To: <20141004050628.4613752a@as> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/04/2014 06:06 AM, Chuck Ebbert wrote: > On Fri, 03 Oct 2014 23:27:58 -0400 > Waiman Long wrote: > >> On 10/03/2014 09:33 AM, Fengguang Wu wrote: >>> Hi Waiman, >>> >>> FYI, we noticed the below changes on commit >>> >>> bd01ec1a13f9a327950c8e3080096446c7804753 ("x86, locking/rwlocks: Enable qrwlocks on x86") >>> >>> +----------------------------------------------+------------+------------+ >>> | | 70af2f8a4f | bd01ec1a13 | >>> +----------------------------------------------+------------+------------+ >>> | boot_successes | 3 | 2 | >>> | boot_failures | 7 | 13 | >>> | BUG:kernel_test_crashed | 7 | 8 | >>> | INFO:rcu_sched_self-detected_stall_on_CPU | 0 | 4 | >>> | RIP:intel_idle | 0 | 4 | >>> | RIP:queue_write_lock_slowpath | 0 | 4 | >>> | RIP:queue_read_lock_slowpath | 0 | 4 | >>> | RIP:sys_imageblit_sysimgblt | 0 | 2 | >>> | RIP:default_send_IPI_mask_sequence_phys | 0 | 1 | >>> | RIP:memcpy | 0 | 1 | >>> | RIP:delay_tsc | 0 | 4 | >>> | backtrace:cpu_startup_entry | 0 | 3 | >>> | backtrace:do_fsync | 0 | 4 | >>> | backtrace:SyS_fsync | 0 | 4 | >>> | backtrace:normal_work_helper | 0 | 1 | >>> | backtrace:vfs_write | 0 | 3 | >>> | backtrace:SyS_write | 0 | 3 | >>> | backtrace:do_sys_open | 0 | 4 | >>> | backtrace:SyS_open | 0 | 4 | >>> | backtrace:flush_to_ldisc | 0 | 1 | >>> | RIP:cpu_startup_entry | 0 | 1 | >>> | RIP:native_read_tsc | 0 | 2 | >>> | RIP:rcu_eqs_exit_common | 0 | 1 | >>> | INFO:rcu_sched_detected_stalls_on_CPUs/tasks | 0 | 1 | >>> +----------------------------------------------+------------+------------+ >>> >>> >> The btrfs filesystem had problem using qrwlock. This was a known btrfs >> problem in 3.16-rc1. The following patch by Chris should have fixed the >> problem: >> >> > commit ea4ebde02e08558b020c4b61bb9a4c0fcf63028e >> > Author: Chris Mason >> > Date: Thu Jun 19 14:16:52 2014 -0700 >> > >> > Btrfs: fix deadlocks with trylock on tree nodes >> >> Was that patch included in your test? >> > That patch went in 3.16-rc2, so it can be assumed it was included in > the test kernel (3.16.0) The problem should be gone in 3.16.0. I was asking because the 2 commits bd01ec1a13 and 70af2f8a4f are the two consecutive qrwlock patches. The first one adds the code while the second one enables its use in x86. So if you just compare these two commits, you will certainly see some regressions in the test. -Longman -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/