public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andi Kleen <ak@suse.de>, lkml <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	dwalker@mvista.com, david singleton <dsingleton@mvista.com>
Subject: Re: 2.6.14-rc4-rt1
Date: Fri, 14 Oct 2005 12:24:25 -0700	[thread overview]
Message-ID: <1129317865.6266.15.camel@localhost.localdomain> (raw)
In-Reply-To: <20051014131250.GA25466@elte.hu>

On Fri, 2005-10-14 at 15:12 +0200, Ingo Molnar wrote:
> * Andi Kleen <ak@suse.de> 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 <asm/errno.h>
>  #include <asm/io.h>
>  
> -#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;

The patch fixed my problem. Machine boots fine.

My next problem. I can't seem to compile the kernel on -rc4-rt1

elm3a242:/usr/src/linux-2.6.14-rc4 # make
  CHK     include/linux/version.h
  SPLIT   include/linux/autoconf.h -> include/config/*
  CC      arch/x86_64/kernel/asm-offsets.s
  GEN     include/asm-x86_64/asm-offsets.h
Trace/breakpoint trap
elm3a242:/usr/src/linux-2.6.14-rc4 # uname -a
Linux elm3a242 2.6.14-rc4-rt1 #4 SMP PREEMPT Fri Oct 14 05:16:35 PDT
2005 x86_64 x86_64 x86_64 GNU/Linux


Thanks,
Badari


  reply	other threads:[~2005-10-14 19:25 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-11 11:14 2.6.14-rc4-rt1 Ingo Molnar
2005-10-11 16:03 ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-11 20:55 ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-11 21:08   ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-11 21:13     ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-11 21:21       ` 2.6.14-rc4-rt1 Lee Revell
2005-10-11 22:23         ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-12 16:37         ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-12 17:48           ` 2.6.14-rc4-rt1 Lee Revell
2005-10-12 18:00             ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-12 18:25               ` 2.6.14-rc4-rt1 Lee Revell
2005-10-12 18:38                 ` 2.6.14-rc4-rt1 Lee Revell
2005-10-12 19:11                   ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-12 19:41                     ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-12 19:45                       ` 2.6.14-rc4-rt1 Lee Revell
2005-10-12 19:52                       ` 2.6.14-rc4-rt1 Lee Revell
2005-10-12  6:14   ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-12  6:16     ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-12  6:33     ` 2.6.14-rc4-rt1 Steven Rostedt
2005-10-12 22:08       ` 2.6.14-rc4-rt1 George Anzinger
2005-10-12 23:41         ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-12 23:52           ` 2.6.14-rc4-rt1 George Anzinger
2005-10-14  4:04           ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-12  7:10     ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-13 22:29       ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-14  2:28         ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-14  4:56           ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-14  6:15             ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-14  8:53               ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-14 18:01               ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-14 18:35                 ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-14 19:05             ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-14  3:56         ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-12 16:42 ` 2.6.14-rc4-rt1 Badari Pulavarty
2005-10-14  6:22   ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-14  9:57     ` 2.6.14-rc4-rt1 Andi Kleen
2005-10-14 13:12       ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-14 19:24         ` Badari Pulavarty [this message]
2005-10-14  6:22   ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-13 21:14 ` 1.6ms jitter in rtc_wakeup (Re: 2.6.14-rc4-rt1) Esben Nielsen
2005-10-14  3:45   ` Ingo Molnar
2005-10-14 21:32     ` Esben Nielsen
2005-10-19  7:52       ` Esben Nielsen
2005-10-19 16:04         ` Petr Vandrovec
2005-10-19 18:07           ` ktimer hiccup in rt11 David Singleton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1129317865.6266.15.camel@localhost.localdomain \
    --to=pbadari@gmail.com \
    --cc=ak@suse.de \
    --cc=dsingleton@mvista.com \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox