From: Jim Potter <jrp@wvi.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: data access errors on 2.4.19-pre3
Date: Thu, 28 Mar 2002 17:12:44 -0800 [thread overview]
Message-ID: <3CA3BF8C.BC3021BC@wvi.com> (raw)
I'm bringing up a recent 2_4_devel kernel (2.4.19-pre3, as I recall) on
our embedded board, and I'm seeing some trap 300's (data access
exception) in printk where it's parsing the string for emit_log_char.
Anyone else seeing this? The target system is a 7450 on 64260,
ppcboot-1.1.5.
--
Sincerely,
Jim Potter
45th Parallel Processing
Those that would give up a necessary freedom for
temporary safety deserve neither freedom nor safety.
-- Ben Franklin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2002-03-29 1:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3CA3BF8C.BC3021BC@wvi.com \
--to=jrp@wvi.com \
--cc=linuxppc-dev@lists.linuxppc.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 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.