From: Scott Wood <scottwood@freescale.com>
To: liulijun <liulijun@ict.ac.cn>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: using srio in linux2.6.34.6 causes kernel panic
Date: Mon, 27 Jul 2015 16:56:11 -0500 [thread overview]
Message-ID: <1438034171.2993.313.camel@freescale.com> (raw)
In-Reply-To: <2015072714264025850711@ict.ac.cn>
On Mon, 2015-07-27 at 14:26 +0800, liulijun wrote:
> I've been struggling with a kernel panic during enumeration of a Rapid IO
> system.
> I am using the AM4140 with Freescale P4080 processor. The Linux
> kernel'version is 2.6.34.6.
That is a very old kernel. If you're using that old kernel because it's a
tree you got from some vendor, please contact them for assistance.
Otherwise, please try again with the latest kernel.
-Scott
next prev parent reply other threads:[~2015-07-27 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 6:26 using srio in linux2.6.34.6 causes kernel panic liulijun
2015-07-27 21:56 ` Scott Wood [this message]
2015-07-28 1:29 ` liulijun
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=1438034171.2993.313.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liulijun@ict.ac.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).