From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Martin, Tim" <tim.martin@viasat.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux on Virtex4
Date: Mon, 19 Jun 2006 17:38:40 -0600 [thread overview]
Message-ID: <528646bc0606191638j64448168ia19d6a97ab81e648@mail.gmail.com> (raw)
In-Reply-To: <821B2170E9E7F04FA38DF7EC21DE48710573FD21@VCAEXCH01.hq.corp.viasat.com>
On 6/19/06, Martin, Tim <tim.martin@viasat.com> wrote:
>
> 1) Is there anything obvious from the kernel panics below that I should
> be looking for? Just the answer "linux 2.4.20 is really fricken old,
> upgrade" is probably the right answer.
I've seen kernel panics when booting large kernel images (>1.5M),
especially when I've welded the kernel image to a system.ace file for
booting via CF. I haven't tracked down the root cause. I use both
2.4 and 2.6, and I've seen kernel panics with both. In your case,
you'll need to decode the backtrace to find out where the kernel is
panicing
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2006-06-19 23:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 23:24 Linux on Virtex4 Martin, Tim
2006-06-19 23:38 ` Grant Likely [this message]
2006-06-21 7:14 ` Filippo Capurso
2006-06-21 7:55 ` Grant Likely
2006-06-22 7:32 ` Filippo Capurso
2006-06-20 5:40 ` Aidan Williams
2006-06-20 6:56 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2006-06-20 15:29 Rick Moleres
2006-06-21 8:46 ` Aidan Williams
2006-06-20 17:53 Martin, Tim
2006-06-21 18:10 Rick Moleres
2006-06-21 20:33 Rick Moleres
2006-07-13 15:46 Rick Moleres
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=528646bc0606191638j64448168ia19d6a97ab81e648@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-embedded@ozlabs.org \
--cc=tim.martin@viasat.com \
/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;
as well as URLs for NNTP newsgroup(s).