Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750740AbVJNNMf (ORCPT ); Fri, 14 Oct 2005 09:12:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750742AbVJNNMf (ORCPT ); Fri, 14 Oct 2005 09:12:35 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:456 "EHLO mx2.mail.elte.hu") by vger.kernel.org with ESMTP id S1750740AbVJNNMf (ORCPT ); Fri, 14 Oct 2005 09:12:35 -0400 Date: Fri, 14 Oct 2005 15:12:50 +0200 From: Ingo Molnar To: Andi Kleen Cc: lkml , Thomas Gleixner , Steven Rostedt , dwalker@mvista.com, david singleton , Badari Pulavarty Subject: Re: 2.6.14-rc4-rt1 Message-ID: <20051014131250.GA25466@elte.hu> References: <20051011111454.GA15504@elte.hu> <1129135337.21743.11.camel@localhost.localdomain> <20051014062212.GA30874@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-ELTE-SpamScore: 0.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=0.0 required=5.9 tests=AWL autolearn=disabled SpamAssassin version=3.0.4 0.0 AWL AWL: From: address is in the auto white-list X-ELTE-VirusStatus: clean Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1610 Lines: 41 * Andi Kleen wrote: > > > I am getting similar segfault on boot problem on 2.6.14-rc4-rt1 on my > > > x86-64 box (with LATENCY_TRACE). > > > > > INIT: version 2.86 booting > > > hotplug[877]: segfault at ffffffff8010f588 rip ffffffff8010f588 rsp > > > 00007fffff8bee68 error 15 > > > > what does the ffffffff8010f588 RIP address map to? You can find out by > > It could be any kernel address that someone injected into user space. > Most likely some problem with the vsyscall page with either signal > handling or gettimeofday. vsyscall code is tricky to hack because you > cannot add any new functions there, just inlines, otherwise the code > won't end up the right section. ah, indeed - i completely forgot about vsyscalls - they must not be traced. Badari, does the patch below help? Ingo Index: linux/arch/x86_64/kernel/vsyscall.c =================================================================== --- linux.orig/arch/x86_64/kernel/vsyscall.c +++ linux/arch/x86_64/kernel/vsyscall.c @@ -34,7 +34,7 @@ #include #include -#define __vsyscall(nr) __attribute__ ((unused,__section__(".vsyscall_" #nr))) +#define __vsyscall(nr) __attribute__ ((unused,__section__(".vsyscall_" #nr))) notrace #define force_inline __attribute__((always_inline)) inline int __sysctl_vsyscall __section_sysctl_vsyscall = 1; - 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/