From: "T Michael Turney" <tmike@recipes4linux.com>
To: "Jinwu Wei(???)" <wjw@mail.ndsc.com.cn>, <linuxppc-dev@ozlabs.org>
Subject: RE: help me for: Oops: kernel access of bad area, sig: 11
Date: Thu, 30 Dec 2004 06:44:36 -0800 [thread overview]
Message-ID: <GEEKLLHMFHLAJOBEEELHGEJMCNAA.tmike@recipes4linux.com> (raw)
In-Reply-To: <002c01c4ee47$254516b0$c7c8a8c0@LocalHost>
[-- Attachment #1: Type: text/plain, Size: 3431 bytes --]
If you are using MVL2.1 why do you have to port ppp_generic.c?
I have used the PPP support already built-in to this kernel without
problem, even ported wvdial/wvstreams to it.
Cheers,
T.mike
-----Original Message-----
From: linuxppc-dev-bounces@ozlabs.org [mailto:linuxppc-dev-bounces@ozlabs.org]On Behalf Of Jinwu Wei(???)
Sent: Thursday, December 30, 2004 12:11 AM
To: linuxppc-dev@ozlabs.org
Subject: help me for: Oops: kernel access of bad area, sig: 11
Importance: High
Dear,
Here is my problems,
Our environmet is:
OS: hardhat Linux 2.1
platform: ppc lopec 7410
uname -r : 2.4.17_mvl21-lopec
When we port the ppp_generic.c(Which is a kernel module), and the program can be executed on host(redhat 7.2). Howerver, when we complied it and runned on ppc lopec7410 (target) by the cross-developemnt enviornment, which can result in the machine down, and when wei return in the beginning of ppp_xmit_process(), the machine is not down but the following massages is printed in the /var/log/massages:
Dec 29 13:52:31 10 kernel: IN ppp_generic.c(ppp_write()):called function ppp_write () 0 times!
Dec 29 13:52:31 10 kernel: In ppp_geberic.c(ppp_file_write()): the send device kind (pf->kind,1=INTERFACE,2=CHANNEL)is 1
Dec 29 13:52:31 10 kernel: In ppp_geberic.c(ppp_file_write()):After copy_from_user, the data from pppd to kernel space is :
Dec 29 13:52:31 10 kernel:
Dec 29 13:52:31 10 kernel: c0 21 01 01 00 0a 02 06 00 00 00 00
Dec 29 13:52:31 10 kernel: IN ppp_GENERIC.c :ppp_xmit_process(),into this function
Dec 29 13:52:31 10 kernel: IN ppp_GENERIC.c :ppp_xmit_process(),ppp->xmit_pending is 0
Dec 29 13:52:32 10 kernel: Oops: kernel access of bad area, sig: 11
Dec 29 13:52:32 10 kernel: NIP: C0012F4C XER: 00000000 LR: C0012F34 SP: DF61FE40 REGS: df61fd90 TRAP: 0300 Tainted: P
Dec 29 13:52:32 10 kernel: MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
Dec 29 13:52:32 10 kernel: DAR: 00000004, DSISR: 42000000
Dec 29 13:52:32 10 kernel: TASK = df61e000[102] 'pppd' Last syscall: 142
Dec 29 13:52:32 10 kernel: last math df61e000 last altivec df61e000
Dec 29 13:52:32 10 kernel: GPR00: 00001032 DF61FE40 DF61E000 00000001 00009032 000000A5 DFDBEDE4 0001F618
Dec 29 13:52:32 10 kernel: GPR08: 0000003C 00000000 DF619008 DF619014 84244862 1004BE28 10040000 10040000
Dec 29 13:52:32 10 kernel: GPR16: 10040000 10040000 10040000 10040000 00009032 DF61FEF8 DF61FE98 0000012C
Dec 29 13:52:32 10 kernel: GPR24: 00000006 00000000 00000145 DF61FED8 C02B0984 DF61900C DF7A35E0 DF619000
Dec 29 13:52:32 10 kernel: Call backtrace:
Dec 29 13:52:32 10 kernel: C0035128 C00516E0 E100379C C0051A28 C0051D30 C0009FD0 C000409C
Dec 29 13:52:32 10 kernel: 1001CBA8 10005EC0 100059B8 0FE69628 00000000
How to debug it and correcte it , Plese help me!
Thanks a lot!
-------------------------------------------
Best Regards
Dr. Jinwu Wei
-----------------------------------------------------------------
National Digital Switching System
Engineering & Technology R&D Center (NDSC),
Jianxue street 7#, Box:1001, No.783,
Zhengzhou, 450002.
Henan province, P.R. China.
Tel: +86-371-3532873
Fax: +86-371-3941700
Email: wjw@mail.ndsc.com.cn
or bstap2000@yahoo.com.cn
[-- Attachment #2: Type: text/html, Size: 8701 bytes --]
prev parent reply other threads:[~2004-12-30 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 8:11 help me for: Oops: kernel access of bad area, sig: 11 Jinwu Wei\(魏进武\)
2004-12-30 14:44 ` T Michael Turney [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=GEEKLLHMFHLAJOBEEELHGEJMCNAA.tmike@recipes4linux.com \
--to=tmike@recipes4linux.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=wjw@mail.ndsc.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