Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755059AbYJOMG0 (ORCPT ); Wed, 15 Oct 2008 08:06:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752594AbYJOMGS (ORCPT ); Wed, 15 Oct 2008 08:06:18 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:38740 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752542AbYJOMGS (ORCPT ); Wed, 15 Oct 2008 08:06:18 -0400 Date: Wed, 15 Oct 2008 14:05:58 +0200 From: Ingo Molnar To: Jeff Chua Cc: lkml , Linus Torvalds , Suresh Siddha , "H. Peter Anvin" , Thomas Gleixner , Jeremy Fitzhardinge Subject: Re: linux 2.6.27 kernel panic on x86 - please revert commit 3a85e770aa77e4f1a4096275c97b64c10cd7323e Message-ID: <20081015120558.GA23347@elte.hu> References: <20081015112324.GB31476@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.1 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.1 required=5.9 tests=BAYES_00,DNS_FROM_SECURITYSAGE,URI_HEX autolearn=no SpamAssassin version=3.2.3 0.4 URI_HEX URI: URI hostname has long hexadecimal sequence -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] 0.0 DNS_FROM_SECURITYSAGE RBL: Envelope sender in blackholes.securitysage.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1799 Lines: 44 * Jeff Chua wrote: > On Wed, Oct 15, 2008 at 7:23 PM, Ingo Molnar wrote: > > > > * Jeff Chua wrote: > > > >> Commit 3a85e770aa77e4f1a4096275c97b64c10cd7323e broke linux boot on > >> x86 resulting in kernel panic. Here's the console output ... > >> > >> Net: Registered protocol family 17 > >> Using IPI No-Shortcut mode > >> RAMDISK: Compressed image found at block 0 > >> VFS: Mounted root (ext2 filesystem (readonly). > >> Freeing unsued kernel memory: 312k freed > >> init[1]: segfault at ffffe01c up b7f0dc28 sp bfc26628 error 5 in ld-2.7.90.so[b7f0b000+1c000] > >> Kernel panic - not syncing: Attempted to kill init! > > > > hm, ffffe01c is weird - VDSO on some ancient distro perhaps? Do you have > > CONFIG_COMPAT_VDSO=y enabled? > > > > if you have CONFIG_COMPAT_VDSO=y enabled but the read access still > > faults, then the question is, why is ffffe000 not mapped properly? The > > logic in arch/x86/vdso/vdso32-setup.c and map_compat_vdso() / > > arch_setup_additional_pages() seems correct and should result in the > > VDSO being mapped as user-readable. > > Didn't realized that CONFIG_COMPAT_VDSO=y could cause this problem. I > had this set long time ago before upgrading to glibc-2.7 > > Unsetting CONFIG_COMPAT_VDSO solves the issue. > > Thanks for your help, and sorry for the fault alarm. Did take a while > to trace it down to the commit. hm, setting the option should not break new glibc so this is a regression and we've still got a bug to fix. Ingo -- 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/