From: Wolfgang Denk <wd@denx.de>
To: "Dross Zhou" <zjuzhou@yahoo.com.cn>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Why system panic after sometimes?
Date: Fri, 10 May 2002 13:37:20 +0200 [thread overview]
Message-ID: <20020510113725.CF7FB1195C@denx.denx.de> (raw)
In-Reply-To: Your message of "Fri, 10 May 2002 17:58:21 +0800." <20020510095821.44488.qmail@web15005.mail.bjs.yahoo.com>
Hello,
in message <20020510095821.44488.qmail@web15005.mail.bjs.yahoo.com> you wrote:
>
> I am sorry i have not described clear.
> We use HardHat CDK1.2's cross compile.
This is pretty old, but should work for this purpose.
> We have not use USB driver yet, I have writed a driver
> for a MPEGI coder chip (operate it via data and
> address bus).I think my driver (just handle interrupts
> from chip) is safe and will not affect kernel
Well, I think the kernel version you are using is very stable, so
maybe it _is_ a problem in your driver?
> and i don't know how to decode backtrace?
See Documentation/oops-tracing.txt in youir LInux kernel source
directory; alternatively, look up the addresses / symbols manually in
the Systems.map file in your kernel directory.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
You got to learn three things. What's real, what's not real, and
what's the difference." - Terry Pratchett, _Witches Abroad_
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-10 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 3:18 Why system panic after sometimes? Dross Zhou
2002-05-10 6:43 ` Wolfgang Denk
2002-05-10 9:58 ` Dross Zhou
2002-05-10 11:37 ` Wolfgang Denk [this message]
2002-05-10 11:53 ` Jerry Van Baren
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=20020510113725.CF7FB1195C@denx.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=zjuzhou@yahoo.com.cn \
/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).