Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751342AbWANWtP (ORCPT ); Sat, 14 Jan 2006 17:49:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751346AbWANWtP (ORCPT ); Sat, 14 Jan 2006 17:49:15 -0500 Received: from tornado.reub.net ([202.89.145.182]:225 "EHLO tornado.reub.net") by vger.kernel.org with ESMTP id S1751342AbWANWtO (ORCPT ); Sat, 14 Jan 2006 17:49:14 -0500 Message-ID: <43C97FE6.8040402@reub.net> Date: Sun, 15 Jan 2006 11:49:10 +1300 From: Reuben Farrelly User-Agent: Thunderbird 1.6a1 (Windows/20060114) MIME-Version: 1.0 To: Andrew Morton CC: Linux Kernel Subject: Re: 2.6.15-mm4 References: <20060114055153.04684592.akpm@osdl.org> In-Reply-To: <20060114055153.04684592.akpm@osdl.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2368 Lines: 73 On 15/01/2006 2:51 a.m., Andrew Morton wrote: > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm4/ > > (Will take an hour or so to mirror) > > > > - Lots of mutex conversions > > - FUSE update > > - nfsd update (mainly nfs4) > > - CPU scheduler update > > - A few new syscalls. A couple of issues to look at with this kernel, it seems. I'll report them one by one, each in a different message so as to work the threading properly. A trace: Freeing unused kernel memory: 196k freed Write protecting the kernel read-only data: 655k Badness in blk_do_ordered at block/ll_rw_blk.c:549 [] show_trace+0xd/0xf [] dump_stack+0x17/0x19 [] blk_do_ordered+0x301/0x306 [] elv_next_request+0x3a/0x120 [] scsi_request_fn+0x57/0x2d5 [] __generic_unplug_device+0x22/0x25 [] generic_unplug_device+0x2c/0x39 [] unplug_slaves+0x5d/0xea [] raid1_unplug+0x11/0x1f [] blk_backing_dev_unplug+0xf/0x11 [] sync_buffer+0x2e/0x37 [] __wait_on_bit+0x45/0x62 [] out_of_line_wait_on_bit+0x6b/0x82 [] __wait_on_buffer+0x27/0x2d [] search_by_key+0x14e/0x11a5 [] reiserfs_read_locked_inode+0x64/0x561 [] reiserfs_iget+0x70/0x88 [] reiserfs_lookup+0xbf/0x10e [] do_lookup+0x105/0x132 [] __link_path_walk+0x11e/0xd4b [] link_path_walk+0x46/0xd2 [] do_path_lookup+0xa9/0x215 [] __path_lookup_intent_open+0x44/0x7f [] path_lookup_open+0x21/0x27 [] open_namei+0x62/0x5a0 [] do_filp_open+0x26/0x43 [] do_sys_open+0x41/0xc2 [] sys_open+0x1c/0x1e [] init+0x193/0x325 [] kernel_thread_helper+0x5/0xb INIT: version 2.86 booting It has never properly blown up into a full detailed oops, just spews out the trace to console and then hangs. I've seen this multiple times today, it is however fatal as every time it has occurred the box needs a reset. reuben - 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/