Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757198AbYBPTqh (ORCPT ); Sat, 16 Feb 2008 14:46:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752450AbYBPTq0 (ORCPT ); Sat, 16 Feb 2008 14:46:26 -0500 Received: from smtp2.linux-foundation.org ([207.189.120.14]:54311 "EHLO smtp2.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752229AbYBPTqY convert rfc822-to-8bit (ORCPT ); Sat, 16 Feb 2008 14:46:24 -0500 Date: Sat, 16 Feb 2008 11:45:27 -0800 From: Andrew Morton To: Kamalesh Babulal Cc: linux-kernel@vger.kernel.org, linux390@de.ibm.com, linux-s390@vger.kernel.org, Andy Whitcroft , Thomas Gleixner Subject: Re: [BUG] 2.6.25-rc2-mm1 - kernel oops while bootup on s390x Message-Id: <20080216114527.48408288.akpm@linux-foundation.org> In-Reply-To: <47B70C3A.4050600@linux.vnet.ibm.com> References: <20080216002522.9c4bd0fb.akpm@linux-foundation.org> <47B70C3A.4050600@linux.vnet.ibm.com> X-Mailer: Sylpheed 2.4.1 (GTK+ 2.8.17; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2602 Lines: 58 On Sat, 16 Feb 2008 21:45:54 +0530 Kamalesh Babulal wrote: > Hi Andrew, > > The 2.6.25-rc2-mm1 kernel panic's while boot up on the s390x > > Unable to handle kernel pointer dereference at virtual kernel address 0000000000 > 000000 > Oops: 0004 #1? SMP > Modules linked in: > CPU: 0 Not tainted 2.6.25-rc2-mm1-autotest #1 > Process swapper (pid: 1, task: 000000003f830000, ksp: 000000003f83ba48) > Krnl PSW : 0704a00180000000 000000000024b2be (futex_atomic_cmpxchg_std+0x12/0x28 > ) > R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:2 CC:2 PM:0 EA:3 > Krnl GPRS: 0000000000000074 00000000fffffff2 0000000000000000 0000000000000000 > 0000000000000000 0000000000000001 0000000000000000 00000000004d0764 > 0000000000000000 00000000004d8768 0000000000000000 000000003f83bdb0 > 0000000000000040 0000000000343950 00000000000627e4 000000003f83bdb0 > Krnl Code: 000000000024b2b2: b90400bf lgr %r11,%r15 > 000000000024b2b6: a718fff2 lhi %r1,-14 > 000000000024b2ba: b2790100 sacf 256 > >000000000024b2be: ba342000 cs %r3,%r4,0(%r2) > 000000000024b2c2: 1813 lr %r1,%r3 > 000000000024b2c4: b2790000 sacf 0 > 000000000024b2c8: b9140021 lgfr %r2,%r1 > 000000000024b2cc: e3b0b0700004 lg %r11,112(%r11) > Call Trace: > (<000000003f83bda8>? 0x3f83bda8) > <00000000004bdeec>? init+0x30/0x104 > <00000000004b0c40>? kernel_init+0x1e0/0x370 > <000000000001a5c6>? kernel_thread_starter+0x6/0xc > <000000000001a5c0>? kernel_thread_starter+0x0/0xc > > <4>--- end trace 561bb236c800851f ?--- > note: swapper1? exited with preempt_count 1 > Kernel panic - not syncing: Attempted to kill init! > Possibilities are that something has gone wrong with the recent cmpxchg changes which are now in mainline, or there's something wrong with futex-fix-init-order.patch or futex-runtime-enable-pi-and-robust-functionality.patch. Or, of course, it's something else ;) First question is: does this happen in current mainline? If not, it would be useful if someone could test futex-fix-init-order.patch and futex-runtime-enable-pi-and-robust-functionality.patch on curent mainline, because those are planned for 2.6.25. Thanks. -- 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/