From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: [PATCHSET] block: per-queue policy activation, take#2 Date: Wed, 25 Apr 2012 11:19:05 -0700 Message-ID: <20120425181905.GA8989@google.com> References: <1334347895-6268-1-git-send-email-tj@kernel.org> <20120420080943.GG7505@kernel.dk> <4F91503D.2060402@kernel.dk> <20120420171742.GC32324@google.com> <4F91B433.2070209@kernel.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=wc/Nx0wDEfaHIp9Y96zRyU3oEvgvMhx4qrc/E1XrdkQ=; b=e18Pkasc+R9xbdPikYlvQSFKWej729lwlqjjg5hTSYwsdMb28/65mT62aAqrVu+k1P zZRQkRKpYTJ5QDN1U8NOX4RI00kKqb2UswqQeQ0jY1XAc/+MumNwTW9m2a2q2juBGlik u8FwX6ulPGDQY6dibZcwccafrLUAdf0WKE//9A5mpNipwODE2MzRsIDMwobclK/kMXAa 7QqsbYzrhz6E/Vx4lXwR+d59g2FHUP0B3Ckbuolo02bDtFsV0pk6iDma6xSNXdHMcave D7Jg3LncVSDM6fs40OzkURVWdPHB/d4GE5NTtmwEEg55wAk321PZtxt9VK1YhGUd0eeu sjQA== Content-Disposition: inline In-Reply-To: <4F91B433.2070209-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Jens Axboe Cc: ctalbott-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org, rni-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org, containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org On Fri, Apr 20, 2012 at 09:08:35PM +0200, Jens Axboe wrote: > On 2012-04-20 19:17, Tejun Heo wrote: > > Hello, Jens. > > > > On Fri, Apr 20, 2012 at 02:02:05PM +0200, Jens Axboe wrote: > >> Tejun, everything merged in cleanly. A boot test didn't not go so well, > >> I'm afraid. It complains about stuck RCU. Even with extra RCU > >> debugging/info turned on, it doesn't give my any extra info. > >> > >> Config is attached. I can try and debug this on Monday, for now I've > >> pulled it out of for-next again. > > > > Hmmm... it works fine with the same config here (qemu w/ 4 cpus > > configured). Doesn't stuck RCU usually come from unbalanced RCU > > lock/unlocking? That should trigger context or RCU warnings before > > anything else, weird. Anyways, it would be great if you can provide > > more info on how to reproduce the problem. > > The machine just sat there. I'll get some more info out of it and run a > bisect too. Any progress on this? Thanks. -- tejun From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757454Ab2DYSTL (ORCPT ); Wed, 25 Apr 2012 14:19:11 -0400 Received: from mail-pz0-f51.google.com ([209.85.210.51]:62230 "EHLO mail-pz0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756340Ab2DYSTK (ORCPT ); Wed, 25 Apr 2012 14:19:10 -0400 Date: Wed, 25 Apr 2012 11:19:05 -0700 From: Tejun Heo To: Jens Axboe Cc: vgoyal@redhat.com, ctalbott@google.com, rni@google.com, linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, containers@lists.linux-foundation.org Subject: Re: [PATCHSET] block: per-queue policy activation, take#2 Message-ID: <20120425181905.GA8989@google.com> References: <1334347895-6268-1-git-send-email-tj@kernel.org> <20120420080943.GG7505@kernel.dk> <4F91503D.2060402@kernel.dk> <20120420171742.GC32324@google.com> <4F91B433.2070209@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F91B433.2070209@kernel.dk> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 20, 2012 at 09:08:35PM +0200, Jens Axboe wrote: > On 2012-04-20 19:17, Tejun Heo wrote: > > Hello, Jens. > > > > On Fri, Apr 20, 2012 at 02:02:05PM +0200, Jens Axboe wrote: > >> Tejun, everything merged in cleanly. A boot test didn't not go so well, > >> I'm afraid. It complains about stuck RCU. Even with extra RCU > >> debugging/info turned on, it doesn't give my any extra info. > >> > >> Config is attached. I can try and debug this on Monday, for now I've > >> pulled it out of for-next again. > > > > Hmmm... it works fine with the same config here (qemu w/ 4 cpus > > configured). Doesn't stuck RCU usually come from unbalanced RCU > > lock/unlocking? That should trigger context or RCU warnings before > > anything else, weird. Anyways, it would be great if you can provide > > more info on how to reproduce the problem. > > The machine just sat there. I'll get some more info out of it and run a > bisect too. Any progress on this? Thanks. -- tejun