[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1237953290.3203.3.camel@localhost.localdomain>
Date: Wed, 25 Mar 2009 03:54:50 +0000
From: Fernando Lopez-Lezcano <nando@...ma.Stanford.EDU>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: nando@...ma.Stanford.EDU, Ingo Molnar <mingo@...e.hu>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Announce] 2.6.29-rc8-rt2
On Tue, 2009-03-24 at 09:12 +0100, Thomas Gleixner wrote:
> On Tue, 24 Mar 2009, Thomas Gleixner wrote:
>
> > On Mon, 23 Mar 2009, Fernando Lopez-Lezcano wrote:
> > > without all the funny numbers this is what remains on screen:
> > >
> > > native_cpu_die
> > > _cpu_down
> > > disable_nonboot_cpus
> > > kernel_power_off
> > > sys_reboot
> > > __hrtimer_start_range_ns
> > > default_spin_lock_flags
> > > __spin_lock_irqsave
> > > __spin_lock_irqrestore
> > > hrtimer_try_to_cancel
> > > hrtimer_cancel
> > > do_nanosleep
> > > hrtimer_nanosleep
> > > hrtimer_wakeup
> > > path_put
> > > audit_syscall_entry
> > > audit_syscall_exit
> > > sysenter_do_call
> > > Code: 00 00 6a 00 ff 15 08 49 85 c0 58 etc etc etc
> > > EIP [<c06f2549>] text_poke+0x163/0x181 SS:ESP 0068:f4567ddc
> >
> > Hmm. Do you have CONFIG_HAVE_DYNAMIC_FTRACE=y in your config ? If yes,
>
> CONFIG_DYNAMIC_FTRACE=y of course.
>
> > can you please disable it ?
First try failed, something else must be requiring it...
> > > -- [end trace db3e80122adba82c ]---
> > > init: rc0 main process (3047) killed by SEGV signal
> > >
> > > (I can take a picture if that would help - I don't have a second machine
> > > with a serial port to try to capture the whole thing)
> >
> > That'd be very helpful.
Snapshot attached... (on my t61 laptop)
-- Fernando
Download attachment "screen1.jpg" of type "image/jpeg" (70377 bytes)
Powered by blists - more mailing lists