From: Thomas Gleixner <tglx@linutronix.de>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Announce] 2.6.29-rc8-rt2
Date: Tue, 24 Mar 2009 09:12:58 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.0903240912360.29264@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0903240907390.29264@localhost.localdomain>
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 ?
>
> > -- [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.
>
> Thanks,
>
> tglx
>
next prev parent reply other threads:[~2009-03-24 8:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 0:57 [Announce] 2.6.29-rc6-rt2 Fernando Lopez-Lezcano
2009-02-24 10:29 ` Thomas Gleixner
2009-02-24 16:30 ` Thomas Gleixner
2009-02-24 22:18 ` Fernando Lopez-Lezcano
2009-02-25 20:52 ` [Announce] 2.6.29-rc6-rt3 (was 2.6.29-rc6-rt2) Fernando Lopez-Lezcano
2009-02-26 3:45 ` Fernando Lopez-Lezcano
2009-03-13 22:53 ` [Announce] 2.6.29-rc7-rt1 Fernando Lopez-Lezcano
2009-03-14 7:46 ` Thomas Gleixner
2009-03-21 18:44 ` [Announce] 2.6.29-rc8-rt2 Fernando Lopez-Lezcano
2009-03-21 18:49 ` Ingo Molnar
2009-03-21 19:06 ` Fernando Lopez-Lezcano
2009-03-21 19:27 ` Fernando Lopez-Lezcano
2009-03-22 2:07 ` Fernando Lopez-Lezcano
2009-03-22 13:09 ` Ingo Molnar
2009-03-22 21:43 ` Fernando Lopez-Lezcano
2009-03-23 8:07 ` Ingo Molnar
2009-03-24 3:13 ` Fernando Lopez-Lezcano
2009-03-24 8:11 ` Thomas Gleixner
2009-03-24 8:12 ` Thomas Gleixner [this message]
2009-03-25 3:54 ` Fernando Lopez-Lezcano
2009-03-25 7:27 ` Thomas Gleixner
2009-03-25 12:57 ` Ingo Molnar
2009-03-25 18:45 ` Fernando Lopez-Lezcano
2009-03-26 3:48 ` Fernando Lopez-Lezcano
-- strict thread matches above, loose matches on Subject: below --
2009-02-11 22:43 [Announce] 2.6.29-rc4-rt1 Thomas Gleixner
2009-02-12 22:56 ` [Announce] 2.6.29-rc4-rt2 Thomas Gleixner
2009-02-23 19:44 ` [Announce] 2.6.29-rc6-rt2 Thomas Gleixner
2009-02-24 17:51 ` Thomas Gleixner
2009-02-24 17:57 ` [Announce] 2.6.29-rc6-rt3 Thomas Gleixner
2009-03-12 19:17 ` [Announce] 2.6.29-rc7-rt1 Thomas Gleixner
2009-03-20 0:31 ` [Announce] 2.6.29-rc78rt1 Thomas Gleixner
2009-03-20 17:45 ` [Announce] 2.6.29-rc8-rt2 Thomas Gleixner
2009-03-20 19:19 ` Will Schmidt
2009-03-20 19:25 ` Ingo Molnar
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=alpine.LFD.2.00.0903240912360.29264@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nando@ccrma.Stanford.EDU \
/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
all inboxes | Powered by JetHome®