public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: Rui Nuno Capela <rncbc@rncbc.org>
Cc: linux-kernel@vger.kernel.org, Mike Galbraith <efault@gmx.de>,
	Karsten Wiese <fzu@wemgehoertderstaat.de>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: realtime-preempt patch-2.6.18-rt7 oops
Date: Sun, 05 Nov 2006 11:02:15 -0500	[thread overview]
Message-ID: <1162742535.2750.23.camel@localhost.localdomain> (raw)
In-Reply-To: <454E15B0.2050008@rncbc.org>

On Sun, 2006-11-05 at 16:47 +0000, Rui Nuno Capela wrote:
> Rui Nuno Capela wrote:
> > After a suggestion from Mike Galbraith, I now turned to pure and
> > original 2.6.18-rt7 and configured with:
> > 
> > CONFIG_FRAME_POINTER=y
> > CONFIG_UNWIND_INFO=y
> > CONFIG_STACK_UNWIND=y
> > 
> > Nasty things still do happen, as the following capture can tell as evidence:
> > 
> 
> Some more evidence, just happening:
> 
> ...
> Oops: 0002 [#1]
>  [<c0106455>] show_trace_log_lvl+0x185/0x1a0
>  [<c0106ae2>] show_trace+0x12/0x20
>  [<c0106c49>] dump_stack+0x19/0x20
>  [<c02f8d2f>] __schedule+0x63f/0xea0
>  [<c02f9700>] schedule+0x30/0x100
>  [<c02fa5db>] rt_spin_lock_slowlock+0x9b/0x1b0
>  [<c02fadb2>] rt_spin_lock+0x22/0x30
>  [<c02fd8b1>] kprobe_flush_task+0x11/0x50
>  [<c02f91fa>] __schedule+0xb0a/0xea0
>  [<c0103b61>] cpu_idle+0xb1/0x120
>  [<c011760f>] start_secondary+0x43f/0x500

Is there more above this log? It looks like your cutting off some stuff
above this.

Daniel


  reply	other threads:[~2006-11-05 18:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-02 10:43 realtime-preempt patch-2.6.18-rt7 oops Rui Nuno Capela
2006-11-03 11:30 ` Karsten Wiese
2006-11-03 22:55   ` Rui Nuno Capela
2006-11-04  2:08     ` Rui Nuno Capela
2006-11-04 10:54       ` Rui Nuno Capela
2006-11-04 15:08         ` Karsten Wiese
2006-11-05 15:55         ` Rui Nuno Capela
2006-11-05 16:47           ` Rui Nuno Capela
2006-11-05 16:02             ` Daniel Walker [this message]
2006-11-05 18:38               ` Rui Nuno Capela
2006-11-05 18:18                 ` Daniel Walker
2006-11-06  7:24                 ` Mike Galbraith
2006-11-06  9:38                   ` Ingo Molnar
2006-11-06 10:02                     ` Mike Galbraith
2006-11-06 10:11                       ` Ingo Molnar
2006-11-06 10:26                         ` Mike Galbraith
2006-11-10  9:31                           ` Rui Nuno Capela
2006-11-10  9:33                             ` 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=1162742535.2750.23.camel@localhost.localdomain \
    --to=dwalker@mvista.com \
    --cc=efault@gmx.de \
    --cc=fzu@wemgehoertderstaat.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rncbc@rncbc.org \
    /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