From: Eugene Surovegin <ebs@ebshome.net>
To: FLAMENT David <d.flament@sofrel.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: help me for: Oops: kernel access of bad area, sig: 11 on rattler 8248 (ppc)
Date: Tue, 12 Jul 2005 02:36:22 -0700 [thread overview]
Message-ID: <20050712093622.GB25918@gate.ebshome.net> (raw)
In-Reply-To: <892C3EC180087B4498C69413FCCBB7320159ADF0@sof_msg>
On Tue, Jul 12, 2005 at 10:07:52AM +0200, FLAMENT David wrote:
> Dear,
>
> Here is my problems,
>
> OS: kernel 2.4.26
> platform: ppc rattler 8248
Publicly available Linux PPC trees don't have support for this board.
Please, direct all your questions to the vendor you got this kernel
form, e.g. Arabella.
We cannot help you, sorry.
Also, next time, use linuxppc-embedded for questions like this.
--
Eugene
prev parent reply other threads:[~2005-07-12 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 8:07 help me for: Oops: kernel access of bad area, sig: 11 on rattler 8248 (ppc) FLAMENT David
2005-07-12 9:36 ` Eugene Surovegin [this message]
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=20050712093622.GB25918@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=d.flament@sofrel.com \
--cc=linuxppc-dev@ozlabs.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 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).