Oops:kernel access of bad areasig:11

Oops:kernel access of bad areasig:11

[hu]

1)environment
Linux kernel 2.4.4-rthal5
ppcboot 1.1.5
MPC823 board

2)I'm running a device driver which read data from touchpanel which use SIU_IRQ2, but I often get message like that:
Oops: kernel access of bad area, sig: 11
NIP: C000C4E8 XER: C000206F LR: C000C4E0 SP: C07FBEF0 REGS: c07fbe40 TRAP: 0300
MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 00000004,DISR: 0000013C
last math 00000000   last altivec 00000000
GPR00: 00000002 C07FBEF0 C07FA000 C07FBF08 00009032 C0C09E58 C0C08000 00000020
GPR08: C01A9138 C0195364 C0C08000 C07FBF30 2F7B6A70 1007C2B8 40024400 00000000
GPR16: 00000000 00000000 00000000 00000000 00000000 00003400 00580000 00002C7E
GPR24: 00000000 0001C200 00000001 C07FBEF8 00000000 C07FBF00 00664BDA C07FBEF0

Call backtrace:
  C000C468 C002B440 C0004DA8

3) I look through past document in linux-embedded, and I check /arch/ppc/kernel/m8xx_setup.c, it exists:
fp = binfo->bi_intfreq * 1000000 / 16;
and /arch/ppc/8xx_io/commproc.c, it exits:
#define BRG_INT_CLK	(((bd_t *)__res)->bi_intfreq * 1000000 )

------------------------------
John Hu
E-mail: hl76@263.net
------------------------------

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Oops:kernel access of bad areasig:11

[Wolfgang Grandegger]

On 07/14/2004 07:33 AM hu wrote:
> 1)environment
> Linux kernel 2.4.4-rthal5
> ppcboot 1.1.5
> MPC823 board
>
> 2)I'm running a device driver which read data from touchpanel which use SIU_IRQ2, but I often get message like that:
> Oops: kernel access of bad area, sig: 11
> NIP: C000C4E8 XER: C000206F LR: C000C4E0 SP: C07FBEF0 REGS: c07fbe40 TRAP: 0300
> MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
> DAR: 00000004,DISR: 0000013C
> last math 00000000   last altivec 00000000
> GPR00: 00000002 C07FBEF0 C07FA000 C07FBF08 00009032 C0C09E58 C0C08000 00000020
> GPR08: C01A9138 C0195364 C0C08000 C07FBF30 2F7B6A70 1007C2B8 40024400 00000000
> GPR16: 00000000 00000000 00000000 00000000 00000000 00003400 00580000 00002C7E
> GPR24: 00000000 0001C200 00000001 C07FBEF8 00000000 C07FBF00 00664BDA C07FBEF0
>
> Call backtrace:
>   C000C468 C002B440 C0004DA8
>
> 3) I look through past document in linux-embedded, and I check /arch/ppc/kernel/m8xx_setup.c, it exists:
> fp = binfo->bi_intfreq * 1000000 / 16;
> and /arch/ppc/8xx_io/commproc.c, it exits:
> #define BRG_INT_CLK	(((bd_t *)__res)->bi_intfreq * 1000000 )

It's difficult to guess from your input what might provoke the error.
Here are few more questions:

- Does the same problem show up with the stanndard (non-RTAI) kernel?
- Is RTAI running, e.g. RTAI modules loaded?
- Have you tried to interpret the backtrace?

And if it really has to do with RTAI, then you are off-topic on this list.

Wolfgang.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Oops:kernel access of bad areasig:11

[Wolfgang Denk]

In message <20040714053136.86F102F86F@smtp.263.net> you wrote:
>
> 1)environment
> Linux kernel 2.4.4-rthal5
> ppcboot 1.1.5
> MPC823 board

Ummm... this is all a bit out of date...

> 2)I'm running a device driver which read data from touchpanel which use SIU_IRQ2, but I often get message like that:
> Oops: kernel access of bad area, sig: 11
...
> Call backtrace:
>   C000C468 C002B440 C0004DA8

OK - and will you please bother to decode these addresses for us?  We
don't have access to your System.map file ...

> 3) I look through past document in linux-embedded, and I check /arch/ppc/kernel/m8xx_setup.c, it exists:
> fp = binfo->bi_intfreq * 1000000 / 16;
> and /arch/ppc/8xx_io/commproc.c, it exits:
> #define BRG_INT_CLK	(((bd_t *)__res)->bi_intfreq * 1000000 )

OK.  Or:
	brg = (unsigned char) (bd->bi_intfreq/(32*2*60000) -3);

What exactly is your problem with that? Looks  OK  to  me.  Different
purposes, different context, different solutions.


Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
For every complex problem, there is a solution that is simple,  neat,
and wrong.                                           -- H. L. Mencken

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/