Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758300AbWK2BAV (ORCPT ); Tue, 28 Nov 2006 20:00:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758313AbWK2BAU (ORCPT ); Tue, 28 Nov 2006 20:00:20 -0500 Received: from twin.jikos.cz ([213.151.79.26]:62117 "EHLO twin.jikos.cz") by vger.kernel.org with ESMTP id S1758300AbWK2BAS (ORCPT ); Tue, 28 Nov 2006 20:00:18 -0500 Date: Wed, 29 Nov 2006 01:59:46 +0100 (CET) From: Jiri Kosina To: Andrew Morton , Neil Brown cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.19-rc6-mm2 In-Reply-To: <20061128020246.47e481eb.akpm@osdl.org> Message-ID: References: <20061128020246.47e481eb.akpm@osdl.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 6440 Lines: 151 On Tue, 28 Nov 2006, Andrew Morton wrote: > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc6/2.6.19-rc6-mm2/ md-change-lifetime-rules-for-md-devices.patch gives me the following early during boot (first WARNING() inside __mutex_lock_slowpath(), then BUG at __mutex_lock_slowpath(), just after that slab corruption). When I revert md-change-lifetime-rules-for-md-devices.patch, everything seems to go fine (this machine does use neither LVM nor RAID, but the kernel has DM compiled in). Config is at http://www.jikos.cz/jikos/junk/.config_md WARNING at kernel/mutex.c:132 __mutex_lock_common() [] dump_trace+0x68/0x1b5 [] show_trace_log_lvl+0x18/0x2c [] show_trace+0xf/0x11 [] dump_stack+0x12/0x14 [] __mutex_lock_slowpath+0xa1/0x213 [] create_dir+0x24/0x1ba [] sysfs_create_dir+0x45/0x5f [] kobject_add+0xce/0x185 [] kobject_register+0x19/0x30 [] md_probe+0x11a/0x124 [] kobj_lookup+0xe6/0x122 [] get_gendisk+0xe/0x1b [] do_open+0x2e/0x298 [] blkdev_open+0x25/0x4d [] __dentry_open+0xc3/0x17e [] nameidata_to_filp+0x24/0x33 [] do_filp_open+0x32/0x39 [] do_sys_open+0x3a/0x66 [] sys_open+0x1c/0x1e [] syscall_call+0x7/0xb DWARF2 unwinder stuck at syscall_call+0x7/0xb Leftover inexact backtrace: ======================= BUG: unable to handle kernel paging request at virtual address 6b6b6b6b printing eip: c01fc5ab *pde = 00000000 Oops: 0000 [#1] SMP last sysfs file: /class/input/input5/event5/dev Modules linked in: video sony_acpi button battery backlight ac ipv6 floppy i2c_viapro i2c_core snd_via82xx gameport snd_ac97_codec snd_ac97_bus snd_seq_dummy via_rhine snd_seq_oss snd_seq_midi_event snd_seq mii snd_pcm_oss snd_mixer_oss snd_pcm pcspkr snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore serio_raw ehci_hcd ohci_hcd uhci_hcd CPU: 0 EIP: 0060:[] Not tainted VLI EFLAGS: 00010046 (2.6.19-rc6-mm2 #1) EIP is at __list_add+0x2a/0x5c eax: 6b6b6b6b ebx: edee9de0 ecx: eb8c34d8 edx: 6b6b6b6b esi: eb8c34b8 edi: 00000246 ebp: ef60a050 esp: edee9db4 ds: 007b es: 007b ss: 0068 Process nash (pid: 1321, ti=edee8000 task=ef60a050 task.ti=edee8000) Stack: 00000001 c0197c7d edee9de0 edee9de0 edee9de0 eb8c34b8 c036e703 00000000 00000002 c0197c7d c03752fd edee9de0 edee9de0 11111111 eb8c34b8 edee9de0 eb882cac ffffffea eb882cac edee9e30 c0197c7d ef60a5a0 00000000 ee8d3404 Call Trace: [] __mutex_lock_slowpath+0xea/0x213 [] create_dir+0x24/0x1ba [] sysfs_create_dir+0x45/0x5f [] kobject_add+0xce/0x185 [] kobject_register+0x19/0x30 [] md_probe+0x11a/0x124 [] kobj_lookup+0xe6/0x122 [] get_gendisk+0xe/0x1b [] do_open+0x2e/0x298 [] blkdev_open+0x25/0x4d [] __dentry_open+0xc3/0x17e [] nameidata_to_filp+0x24/0x33 [] do_filp_open+0x32/0x39 [] do_sys_open+0x3a/0x66 [] sys_open+0x1c/0x1e [] syscall_call+0x7/0xb DWARF2 unwinder stuck at syscall_call+0x7/0xb Leftover inexact backtrace: ======================= no locks held by nash/1321. Code: c3 56 53 89 c3 83 ec 10 8b 41 04 39 d0 74 1c 89 4c 24 0c 89 54 24 04 89 44 24 08 c7 04 24 80 94 3a c0 e8 be f9 f1 ff 0f 0b eb fe <8b> 32 39 ce 74 1c 89 54 24 0c 89 74 24 08 89 4c 24 04 c7 04 24 EIP: [] __list_add+0x2a/0x5c SS:ESP 0068:edee9db4 <3>BUG: sleeping function called from invalid context at kernel/rwsem.c:20 in_atomic():0, irqs_disabled():1 no locks held by nash/1321. [] dump_trace+0x68/0x1b5 [] show_trace_log_lvl+0x18/0x2c [] show_trace+0xf/0x11 [] dump_stack+0x12/0x14 [] down_read+0x15/0x4e [] __blocking_notifier_call_chain+0x11/0x3d [] blocking_notifier_call_chain+0x17/0x1a [] do_exit+0x19/0x782 [] die+0x20c/0x231 [] do_page_fault+0x450/0x51e [] error_code+0x7c/0x84 DWARF2 unwinder stuck at error_code+0x7c/0x84 Leftover inexact backtrace: [] __list_add+0x2a/0x5c [] create_dir+0x24/0x1ba [] __mutex_lock_slowpath+0xea/0x213 [] create_dir+0x24/0x1ba [] create_dir+0x24/0x1ba [] sysfs_create_dir+0x45/0x5f [] kobject_add+0xce/0x185 [] init_waitqueue_head+0x12/0x20 [] kobject_init+0x5b/0x7d [] kobject_register+0x19/0x30 [] md_probe+0x11a/0x124 [] kobj_lookup+0xe6/0x122 [] md_probe+0x0/0x124 [] blkdev_open+0x0/0x4d [] get_gendisk+0xe/0x1b [] do_open+0x2e/0x298 [] blkdev_open+0x0/0x4d [] blkdev_open+0x0/0x4d [] blkdev_open+0x25/0x4d [] __dentry_open+0xc3/0x17e [] nameidata_to_filp+0x24/0x33 [] do_filp_open+0x32/0x39 [] get_unused_fd+0xaa/0xb4 [] _spin_unlock+0x14/0x1c [] get_unused_fd+0xaa/0xb4 [] do_sys_open+0x3a/0x66 [] sys_open+0x1c/0x1e [] syscall_call+0x7/0xb ======================= Slab corruption: start=eb8c3428, len=488 Redzone: 0x5a2cf071/0x5a2cf071. Last user: [](iput+0x60/0x62) 090: 6b 6b 6b 6b 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b Single bit error detected. Probably bad RAM. Run memtest86+ or a similar memory test tool. Prev obj: start=eb8c3234, len=488 Redzone: 0x5a2cf071/0x5a2cf071. Last user: [](iput+0x60/0x62) 000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b Next obj: start=eb8c361c, len=488 Redzone: 0x170fc2a5/0x170fc2a5. Last user: [](alloc_inode+0x22/0x15b) 000: 00 00 00 00 00 00 00 00 28 77 8b eb f4 cd f2 eb 010: 20 38 8c eb fc cd f2 eb ac 6a f5 eb ac 6a f5 eb device-mapper: multipath: version 1.0.5 loaded -- Jiri Kosina - 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/