From: Filip Onkelinx <Filip@Linux4.Be>
To: linux-mips@linux-mips.org
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Subject: Re: "Can't analyze prologue code ..." at boot time
Date: Sat, 25 Sep 2004 00:15:16 +0200 [thread overview]
Message-ID: <41549C74.3090309@Linux4.Be> (raw)
In-Reply-To: <20040924121107.GB24730@enix.org>
Hi Atsushi,
I just applied your patch to our current 2.6.9-rc2 kernel for the BE300
project (Casio BE300/BE500 PDA with NEC vr4131 rev1.2), and the
"Couldn't analyze prologue code .." message is gone as well.
Before, the kernel was very unreliable, but I also sync'ed with the
latest from CVS and switched gcc version , so I'm not sure if it is your
patch that's responsible for the stabiltity or one of the other changes.
thanks,
Filip.
Thomas Petazzoni wrote:
>Hello,
>
>On Fri, Sep 24, 2004 at 07:06:40PM +0900, Atsushi Nemoto wrote :
>
>
>
>>I rewrote get_wchan() to handle this problem. Please try this patch.
>>
>>
>
>This patch works for me. At least, the "Couldn't analyze prologue code
>at ..." message doesn't appear anymore.
>
>Thanks,
>
>Thomas
>
>
--
----
Do not follow where the path may lead. Go instead where there is no path and leave a trail - Ralph Waldo Emerson
----
Filip Onkelinx
Heidebloemstraat 20, B-3500 Hasselt, BELGIUM
fax: +32 11 65 65 97, mobile: +32 475 69 47 63
filip@onkelinx.com
next prev parent reply other threads:[~2004-09-24 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 8:52 "Can't analyze prologue code ..." at boot time Thomas Petazzoni
2004-09-24 10:06 ` Atsushi Nemoto
2004-09-24 12:11 ` Thomas Petazzoni
2004-09-24 22:15 ` Filip Onkelinx [this message]
2004-09-25 14:03 ` Atsushi Nemoto
2004-10-28 15:07 ` Atsushi Nemoto
2004-10-29 11:18 ` Atsushi Nemoto
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=41549C74.3090309@Linux4.Be \
--to=filip@linux4.be \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.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