Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750787AbWEDAbU (ORCPT ); Wed, 3 May 2006 20:31:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750805AbWEDAbU (ORCPT ); Wed, 3 May 2006 20:31:20 -0400 Received: from mx1.redhat.com ([66.187.233.31]:45960 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S1750787AbWEDAbU (ORCPT ); Wed, 3 May 2006 20:31:20 -0400 Date: Wed, 3 May 2006 20:31:16 -0400 From: Dave Jones To: Linux Kernel Subject: spinlock recursion bug (2.6.17rc3) Message-ID: <20060504003116.GA3350@redhat.com> Mail-Followup-To: Dave Jones , Linux Kernel Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1643 Lines: 37 I was moving a 1.2G file over an NFS mount, and wondered why it had stalled making no progress. Then my X session locked up completely, however I was able to ssh in. running free showed that it was *really* low on memory, yet there was a ton of stuff in buffers/caches. It sat there spinning for about 10 minutes making no progress at all In desperation, I tried throwing away those caches with.. echo 3 > /proc/sys/vm/drop_caches And then got this over serial console before the box locked up completely. BUG: spinlock cpu recursion on CPU#1, rhythmbox/31182 lock: ffffffff80547e80, .magic: dead4ead, .owner: bash/32124, .owner_cpu: 1 Call Trace: {spin_bug+176} {bdev_test+0} {_raw_spin_lock+88} {ifind+35} {iget5_locked+112} {bdev_set+0} {blkdev_open+0} {bdget+63} {bd_acquire+71} {blkdev_open+19} {__dentry_open+217} {do_filp_open+42} {cache_alloc_debugcheck_after+307} {get_unused_fd+249} {do_sys_open+68} {tracesys+209} On reboot, I tried to repeat the same operation, and it worked just fine. Hrmph. Dave -- http://www.codemonkey.org.uk - 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/