From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.77) (envelope-from ) id 1SlAb8-0000F6-1s for garchives@archives.gentoo.org; Sun, 01 Jul 2012 03:13:18 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E3ED5E07EE; Sun, 1 Jul 2012 03:12:58 +0000 (UTC) Received: from mail-qc0-f181.google.com (mail-qc0-f181.google.com [209.85.216.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 5F02AE065A for ; Sun, 1 Jul 2012 03:11:13 +0000 (UTC) Received: by qcpx40 with SMTP id x40so2975932qcp.40 for ; Sat, 30 Jun 2012 20:11:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=sveG8QsW8btNBAJlcO/20X6W+vSr/5Ljd2Pjx0Ro9Kw=; b=G498OvwtE5fVEzYtRmuxYepyzR4MjSL5VnkIGPNqJ+Hxcpex9AeFvtvw23FTOSqtD2 8co4fCKU6s7H6T2RH1V5RKtP90yTL9aWRNgfmhHDBzLi6RkDLP05z6jeD992CEvKEe3p jXdHCZWKq9Mb64Z0HLDnSEmUBrQ6jImXmyqE57u2n3joVYfpHtN+QtSR3nb6p09+0nRy rsgkhmwTdcpq5UnW0Nxl4XkmFrIKMh+FiW6UdO+1gZVYYjO7xCJMRXIblsWmJelVzgap +J0QDQjz+a4FSqVPymNpcavKgdwiDSNyovSipwHEWGajnExU/JmJOPIURbcVnkDlS6Bz 53Kw== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.224.138.147 with SMTP id a19mr14430805qau.84.1341112273242; Sat, 30 Jun 2012 20:11:13 -0700 (PDT) Received: by 10.229.227.14 with HTTP; Sat, 30 Jun 2012 20:11:13 -0700 (PDT) In-Reply-To: References: Date: Sat, 30 Jun 2012 21:11:13 -0600 Message-ID: Subject: Re: [gentoo-user] unstoppable, undeciperable kernel call trace in log From: Maxim Wexler To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 26119403-20f5-41b7-bde2-1e15ef8ff8ab X-Archives-Hash: 2eb6b75bf2ee53f14ccd0707df2dfa71 > Hi, > > I don't have an answer, but if you google the phrase "rcu_bh detected > stall on CPU" you can find many reports similar to yours and maybe > some information. This might be usefu lhttp://www.kernel.org/doc/Documentation/RCU/stallwarn.txt "RCU bugs can often be debugged with the help of CONFIG_RCU_TRACE" from in menuconfig. =E2=94=82 This option provides tracing in RCU which presents stats = =E2=94=82 =E2=94=82 in debugfs for debugging RCU implementation. Ok, so I've set the RCU_TRACE=3Dy. Next question: How do I use debugfs, never used it before? > > Do you have RCU_CPU_STALL_INFO=3Dy in your kernel config? no. syzygy@lumby ~ $ grep RCU /usr/src/linux/.config # RCU Subsystem CONFIG_TREE_RCU=3Dy # CONFIG_PREEMPT_RCU is not set # CONFIG_RCU_TRACE is not set CONFIG_RCU_FANOUT=3D32 # CONFIG_RCU_FANOUT_EXACT is not set # CONFIG_RCU_FAST_NO_HZ is not set # CONFIG_TREE_RCU_TRACE is not set # CONFIG_SPARSE_RCU_POINTER is not set CONFIG_RCU_CPU_STALL_TIMEOUT=3D60