From: Scott Wood <scottwood@freescale.com>
To: Dan Malek <dan@embeddedalley.com>
Cc: poorbeyond <poorbeyond@163.com>,
Linux-ppc mail list <linuxppc-embedded@ozlabs.org>
Subject: Re: my cpu is MPC860, kernel version is 2.6.20.14, the kernel start info in the mail. why does the kernel panic?
Date: Mon, 06 Aug 2007 16:24:06 -0500 [thread overview]
Message-ID: <46B79176.6080308@freescale.com> (raw)
In-Reply-To: <A3D38E79-6921-4C9A-BD82-5796B8995BA4@embeddedalley.com>
Dan Malek wrote:
> On Aug 6, 2007, at 8:52 AM, Scott Wood wrote:
>
>> It wouldn't surprise me if the 8xx code has issues with PREEMPT; try
>> turning it off for now.
>
>
> What is your reason that 8xx would be any different?
It's just a suspicion based on my dealings with the CPM code, and the
fact that the crash appeared to happen in the CPM ethernet driver. It
could be wrong, but it doesn't hurt to try without PREEMPT and see if
the problem remains.
-Scott
next prev parent reply other threads:[~2007-08-06 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 10:54 my cpu is MPC860, kernel version is 2.6.20.14, the kernel start info in the mail. why does the kernel panic? poorbeyond
2007-08-06 15:52 ` Scott Wood
2007-08-06 21:12 ` Dan Malek
2007-08-06 21:24 ` Scott Wood [this message]
2007-08-09 15:27 ` Re: my cpu is MPC860, kernel version is 2.6.20.14, the kernel startinfo " poorbeyond
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=46B79176.6080308@freescale.com \
--to=scottwood@freescale.com \
--cc=dan@embeddedalley.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=poorbeyond@163.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).