From: Marc Zyngier <maz@misterjones.org>
To: "Rogério Brito" <rbrito@ime.usp.br>
Cc: linuxppc-dev@ozlabs.org, debian-powerpc@lists.debian.org,
linuxppc-embedded@ozlabs.org
Subject: Re: Call Trace and scary messages on kernel 2.6.27-rc5
Date: Tue, 9 Sep 2008 22:08:55 +0200 [thread overview]
Message-ID: <20080909220855.658b967c@why> (raw)
In-Reply-To: <20080909004727.GA6239@ime.usp.br>
On Mon, 8 Sep 2008 21:47:29 -0300
Rog=C3=A9rio Brito <rbrito@ime.usp.br> wrote:
> Hi there.
>=20
> I just compiled a new 2.6.27-rc5 kernel for my standard Kurobox (an
> embedded NAS that has an MPC8241 CPU, if I'm not mistaken) and upon
> booting, I get these scary messages and Call Traces:
[snip]
This is a known problem.
Check patch bb23b431db7405f6d79f989ad0236bf6428ba1cb in Linus' tree, it
should correct the traces you see.
Regards,
M.
--=20
And if you don't know where you're going, any road will take you there.
next prev parent reply other threads:[~2008-09-09 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 0:47 Call Trace and scary messages on kernel 2.6.27-rc5 Rogério Brito
2008-09-09 0:52 ` Rogério Brito
2008-09-09 6:33 ` Heiko Schocher
2008-09-09 20:08 ` Marc Zyngier [this message]
2008-09-11 5:34 ` Rogério Brito
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=20080909220855.658b967c@why \
--to=maz@misterjones.org \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rbrito@ime.usp.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.