Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755587AbZJ3LLS (ORCPT ); Fri, 30 Oct 2009 07:11:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754931AbZJ3LLR (ORCPT ); Fri, 30 Oct 2009 07:11:17 -0400 Received: from gw3.lbox.cz ([62.245.111.133]:50291 "EHLO develbox.linuxbox.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751311AbZJ3LLR (ORCPT ); Fri, 30 Oct 2009 07:11:17 -0400 X-Greylist: delayed 340 seconds by postgrey-1.27 at vger.kernel.org; Fri, 30 Oct 2009 07:11:16 EDT Date: Fri, 30 Oct 2009 12:06:32 +0100 From: Nikola Ciprich To: Linux kernel list Cc: nikola.ciprich@linuxbox.cz Subject: 2.6.31.4 panic: CRED: put_cred_rcu() sees ffff880204e58c00 with usage 82150912 Message-ID: <20091030110632.GC6416@develbox.linuxbox.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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: 3035 Lines: 55 Hi, some time ago, I updated my KVM hosting machine to 2.6.31.1 and it just died horribly: 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 -- ------------------------------------- Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: servis@linuxbox.cz ------------------------------------- -- 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/