From: Juergen Beisert <juergen127@kreuzholzen.de>
To: linuxppc-embedded@ozlabs.org
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [Trace how to] Kernel Bug when entering something after login
Date: Thu, 26 Jul 2007 14:45:29 +0200 [thread overview]
Message-ID: <200707261445.30391.juergen127@kreuzholzen.de> (raw)
In-Reply-To: <f87351060707260534k2f87ff47rdcfd0b787d5a0132@mail.gmail.com>
On Thursday 26 July 2007 14:34, Pradyumna Sampath wrote:
> Hi Everyone,
>
> On 7/26/07, Juergen Beisert <juergen127@kreuzholzen.de> wrote:
> > On Wednesday 25 July 2007 21:06, Thomas Gleixner wrote:
> > > Solution below
> >
> > Seems to work now. Thanks.
> >
> > Juergen
> > -
>
> First of all very sorry to cross post.
>
> I discovered the same problem on our MPC5200 and it after patching, it
> now works. But I could somehow not get the call trace and hence could
> not report the bug.
>
> I compiled the kernel with "CONFIG_FUNCTION_TRACE" and then I get
> undefined references on "early_printk". Is there something I am doing
> wrong in the kernel config or was there an additional patch to enable
> this support for MPC5200 ?
>
> I see more bugs when I run "stress" but I cant solve them or even
> report them, because I cant see the trace information.
Activate "General setup" -> "Configure standard kernel features (for small
systems)" -> "Load all symbols for debugging/ksymoops"
Juergen
prev parent reply other threads:[~2007-07-26 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200707251900.47704.juergen127@kreuzholzen.de>
[not found] ` <1185390398.3227.8.camel@chaos>
[not found] ` <200707261000.25465.juergen127@kreuzholzen.de>
2007-07-26 12:34 ` [Trace how to] Kernel Bug when entering something after login Pradyumna Sampath
2007-07-26 12:45 ` Juergen Beisert [this message]
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=200707261445.30391.juergen127@kreuzholzen.de \
--to=juergen127@kreuzholzen.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=linuxppc-embedded@ozlabs.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