Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752593AbZKCOqz (ORCPT ); Tue, 3 Nov 2009 09:46:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751261AbZKCOqy (ORCPT ); Tue, 3 Nov 2009 09:46:54 -0500 Received: from mx1.redhat.com ([209.132.183.28]:22406 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751105AbZKCOqx (ORCPT ); Tue, 3 Nov 2009 09:46:53 -0500 Date: Tue, 3 Nov 2009 12:46:38 -0200 From: Marcelo Tosatti To: Nikola Ciprich Cc: Linux kernel list , nikola.ciprich@linuxbox.cz, KVM list Subject: Re: 2.6.31.4 panic: CRED: put_cred_rcu() sees ffff880204e58c00 with usage 82150912 Message-ID: <20091103144638.GE10084@amt.cnet> References: <20091030110632.GC6416@develbox.linuxbox.cz> <20091030111534.GD6416@develbox.linuxbox.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091030111534.GD6416@develbox.linuxbox.cz> User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3168 Lines: 52 On Fri, Oct 30, 2009 at 12:15:34PM +0100, Nikola Ciprich wrote: > Ouch, typo in subject, it's 2.6.31.1 of course. sorry about that. > also CCing kvm. > n. > > On Fri, Oct 30, 2009 at 12:06:32PM +0100, Nikola Ciprich wrote: > > Hi, > > some time ago, I updated my KVM hosting machine to 2.6.31.1 and it just died horribly: Nikola, Upgraded from what? Did you see experience the crash again? > > Oct 30 10:45:17 vbox [706369.133516] Kernel panic - not syncing: CRED: put_cred_rcu() sees ffff880204e58c00 with usage 82150912 > > Oct 30 10:45:17 vbox [706369.133519] > > Oct 30 10:45:17 vbox [706369.144990] Pid: 19, comm: ksoftirqd/5 Not tainted 2.6.31lb.02 #1 > > Oct 30 10:45:17 vbox [706369.151554] Call Trace: > > Oct 30 10:45:17 vbox [706369.154332] > > Oct 30 10:45:17 vbox [] panic+0xaa/0x180 > > Oct 30 10:45:17 vbox [706369.160280] [] ? _spin_unlock+0x30/0x60 > > Oct 30 10:45:17 vbox [706369.166256] [] ? add_partial+0x21/0x90 > > Oct 30 10:45:17 vbox [706369.172155] [] ? __slab_free+0x92/0x3c0 > > Oct 30 10:45:17 vbox [706369.178127] [] ? file_free_rcu+0x37/0x50 > > Oct 30 10:45:17 vbox [706369.184198] [] put_cred_rcu+0x75/0x80 > > Oct 30 10:45:17 vbox [706369.190008] [] __rcu_process_callbacks+0x125/0x250 > > Oct 30 10:45:17 vbox [706369.197020] [] rcu_process_callbacks+0x39/0x60 > > Oct 30 10:45:17 vbox [706369.203624] [] __do_softirq+0xc1/0x250 > > Oct 30 10:45:17 vbox [706369.209506] [] ? ksoftirqd+0x0/0x1a0 > > Oct 30 10:45:17 vbox [706369.215182] [] call_softirq+0x1c/0x30 > > Oct 30 10:45:17 vbox [706369.220986] [] do_softirq+0x3d/0x80 > > Oct 30 10:45:17 vbox [706369.227317] [] ? ksoftirqd+0x0/0x1a0 > > Oct 30 10:45:17 vbox [706369.233020] [] ksoftirqd+0x84/0x1a0 > > Oct 30 10:45:17 vbox [706369.238622] [] kthread+0xa6/0xb0 > > Oct 30 10:45:17 vbox [706369.243956] [] child_rip+0xa/0x20 > > Oct 30 10:45:17 vbox [706369.249390] [] ? kthread+0x0/0xb0 > > Oct 30 10:45:17 vbox [706369.254806] [] ? child_rip+0x0/0x20 > > Oct 30 10:45:17 vbox [706369.260454] Rebooting in 10 seconds.. > > (trace is obtained from netconsole, so hopefully it's not mangled). > > The machine was running ~30 KVM guests, it's 8CPU 16GB x86_64, when it crashed, it was only > > moderately loaded. Never had this (or any other) kind of crash on it before. > > I know there's 2.6.31.5 already out, but I'm not sure if some related problem has been > > reported/fixed and I'm obviously not able to quicky test/reproduce it with latest kernel, > > so I'm rather reporting. > > Should more information/testing/etc be required, I'll be glad to help > > regards > > nik -- 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/