Re: help: why show "Oops: kernel access of bad area, sig: 11"

Re: help: why show "Oops: kernel access of bad area, sig: 11"

[linas]

Hi,

On Mon, May 19, 2003 at 04:33:49PM +0800, guo_zhenglin wrote:
>       Serial driver version 5.05c (2001-07-08) with no serial options
> enabled
>     Oops: kernel access of bad area, sig: 11
>     NIP: C0076F0C XER: 80009E6C LR: C007B620 SP: C017DE80 REGS: c017ddd0
> TRAP: 0300d
> MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
> DAR: 000003F9, DSISR: 00018469
> TASK = c017c000[1] 'swapper' Last syscall: 120
> last math 00000000 last altivec 00000000
> GPR00: 00000000 C017DE80 C017C000 C017DE88 00000001 00000000 C0D203B8
> 000003F8
> GPR08: 00000000 000003F8 00000000 00000000 0000000D FFFFFFFF C007AC70
> C007A4C4
> GPR16: C0079010 C0079CDC C007A5E0 C00770A8 C007701C C007A154 C00790E0
> C0079058
> GPR24: C0079D64 C0078F90 C0078F78 C00F28F8 C00F28F8 C011A76C C011A830
> C017DE88
> Call backtrace:
> C0011AE4 C0101028 C00FA5FC C00FA644 C00022CC C0006BE4
> Kernel panic: Attempted to kill init!
>  <0>Rebooting in 180 seconds..


You need to use System.map to figure out what routine this crashed in.
You need a backtrace/stack dump

Then you need to create assembly for the file in question:
gcc -Wa,ah, -Wa,al

and figure out what the assembly was doing when it crashed.  And then
read the source code to see why.

KDB makes this a *lot* easier.

--linas


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

Re: help: why show "Oops: kernel access of bad area, sig: 11"

[Trevor Woerner]

On May 19, 2003 04:33 am, guo_zhenglin wrote:
>     Oops: kernel access of bad area, sig: 11
>     NIP: C0076F0C XER: 80009E6C LR: C007B620 SP: C017DE80 REGS:
> c017ddd0 TRAP: 0300d
> MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
> DAR: 000003F9, DSISR: 00018469
> TASK = c017c000[1] 'swapper' Last syscall: 120
> last math 00000000 last altivec 00000000
> GPR00: 00000000 C017DE80 C017C000 C017DE88 00000001 00000000 C0D203B8
> 000003F8
> GPR08: 00000000 000003F8 00000000 00000000 0000000D FFFFFFFF C007AC70
> C007A4C4
> GPR16: C0079010 C0079CDC C007A5E0 C00770A8 C007701C C007A154 C00790E0
> C0079058
> GPR24: C0079D64 C0078F90 C0078F78 C00F28F8 C00F28F8 C011A76C C011A830
> C017DE88
> Call backtrace:
> C0011AE4 C0101028 C00FA5FC C00FA644 C00022CC C0006BE4
> Kernel panic: Attempted to kill init!
>  <0>Rebooting in 180 seconds..

When you get an "access of bad area" oops have a look at the DEAR
register (I think you misspelled it as DAR above).

0x3f9 is the base address of COM1 on an x86 machine
(http://www.sput.nl/hardware/io.html). My guess is you've got something
wrong with your UART code. I believe this is where your (current)
problem lies.

Just a guess.
	Trevor

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

RE: help: why show "Oops: kernel access of bad area, sig: 11"

[Dave Ellis]

guo_zhenglin wrote:

> ppcboot 2.0 use MHZ to set bi_intfreq , while kernel 2.4.20 consider
> bi_intfreq as HZ.

You should configure PPCBoot properly to match the kernel. This has
been configurable for a long time. See the PPCBoot README
re CONFIG_CLOCKS_IN_MHZ.

It has been discussed many times on the ppcboot-users list, for
example see:

http://sourceforge.net/mailarchive/message.php?msg_id=479868

BTW clocks_in_mhz must be _removed_ from the environment to
get the clocks in HZ. Setting the value 0 does not work.

Dave

Dave Ellis
~~~~~~~~~~~~~~~~~~~~~~~~~~
SIXNET - "Leading the Industrial Ethernet Revolution"
331 Ushers Road,   P.O. Box 767, Clifton Park, NY 12065 USA
Tel +1 (518) 877-5173   Fax +1 (518) 877-8346
Email me at: dge@sixnetio.com
Detailed product info: www.sixnetio.com
~~~~~~~~~~~~~~~~~~~~~~~~~~


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

Ethernet support for FADS board (MPC823)

[Rupesh S]

Hi,
I work with a FADS823 board. I use u-boot as my bootloader,I downloaded the
ppc kernel from Montavista using rsync. I compiled my kernel with minimal
configurations .It boots and works well on board.
Now that I am trying to add more features like Ethernet support etc etc..
I understand that in our board (FADS823) the Ethernet is on SCC2.When I
configure my kernel for the same in CPM iOptions, it gives me the following
error,

/***************************************************************************
****************************************************************************
**/
make[2]: Entering directory
`/home/rupesh/PPC-Installs/RSYNC/Montavista/linux/arch/ppc/8xx_io'
ppc-linux-gcc -D__KERNEL__ -I/home/rupesh/PPC-Installs/RSYNC/Montavista/linu
x/include -I/usr/lib/gcc-lib/ppc-linux/2.95.4/include/ -Wall -Wstrict-protot
ypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointe
r -I/home/rupesh/PPC-Installs/RSYNC/Montavista/linux/arch/ppc -fsigned-char
-msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring -mcpu=8
60   -nostdinc -iwithprefix include -DKBUILD_BASENAME=enet  -c -o enet.o
enet.c
enet.c:699: #error Exactly ONE pair of PA_ENET_[RT]XD, PB_ENET_[RT]XD must
be defined
enet.c:904: #error Configuration Error: define exactly ONE of PB_ENET_TENA,
PC_ENET_TENA
enet.c: In function `scc_enet_init':
enet.c:713: `PC_ENET_CLSN' undeclared (first use in this function)
enet.c:713: (Each undeclared identifier is reported only once
enet.c:713: for each function it appears in.)
enet.c:713: `PC_ENET_RENA' undeclared (first use in this function)
enet.c:719: `PA_ENET_TCLK' undeclared (first use in this function)
enet.c:719: `PA_ENET_RCLK' undeclared (first use in this function)
enet.c:725: `SICR_ENET_MASK' undeclared (first use in this function)
enet.c:726: `SICR_ENET_CLKRT' undeclared (first use in this function)
enet.c:929: `PB_ENET_TENA' undeclared (first use in this function)
make[2]: *** [enet.o] Error 1
make[2]: Leaving directory
`/home/rupesh/PPC-Installs/RSYNC/Montavista/linux/arch/ppc/8xx_io'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory
`/home/rupesh/PPC-Installs/RSYNC/Montavista/linux/arch/ppc/8xx_io'
make: *** [_dir_arch/ppc/8xx_io] Error 2

/***************************************************************************
****************************************************************************
**/

When I see the comproc.h file, these Macros aen't defined for FADS Board..
What do I do?
Any clues ?

Rupesh

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

X-Engine over Video Controller

[Rupesh S]

Hi,

I work with FADS823 board running PPC-Linux.
Now that I plan to put a X-Engine over my Video Controller inbuilt in MPC823
and supported by FADS board.
Need help in selecting the X-Engine and the feasibility of the same with the
above mentioned board.
Also I would like to know if I can get any ind of reference for the same....

Rupesh


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