Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 17 Jul 2002 16:07:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 17 Jul 2002 16:07:40 -0400 Received: from mailrelay.ds.lanl.gov ([128.165.47.40]:13981 "EHLO mailrelay.ds.lanl.gov") by vger.kernel.org with ESMTP id ; Wed, 17 Jul 2002 16:06:55 -0400 Subject: 2.5.25-dj2, kernel BUG at dcache.c:361 From: Steven Cole To: Dave Jones Cc: linux-kernel@vger.kernel.org, Steven Cole Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2-5mdk Date: 17 Jul 2002 14:06:50 -0600 Message-Id: <1026936410.11636.107.camel@spc9.esa.lanl.gov> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1065 Lines: 29 While running 2.5.25-dj2 and dbench with increasing numbers of clients, my test machine locked up with the following message: kernel BUG at dcache.c:361! I tried to copy down the following register dump but was unable to. Nothing interesting saved in /var/log/messages. This is fairly repeatable in that it happens with running dbench with more than 32 clients. I saw it once with as few as 6 clients. After getting weary of running fsck on an ext2 /home partition, I added a journal to /home and mounted it as ext3. With /home (where dbench is running) mounted as ext3, I got the following message just before the BUG: EXT3-fs error (device sd(8,8): ext3_free_blocks: freeing blocks not in datazone - block = 7939096, count = 13. The test machine is a dual p3 1mb memory, scsi, 2.5.25-dj2 SMP kernel. Steven - 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/