Home/Support/Support Forum/Digi CM 16 - Boot Failure Kernel Panic: Oops: kernel access of bad area, sig: 11
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

Digi CM 16 - Boot Failure Kernel Panic: Oops: kernel access of bad area, sig: 11

0 votes
Doing a new project and resurecting a Digi CM16. No PCMCIA Device installed.

Connected via Serial cable. Boot giving kernel panic. Need to see if anyone can point me to the manual to repair / debug.

Boot Output:
************************************

Bootloader 1.0.0 (Mar 4 2003 - 18:02:52)

CPU : XPC855xxZPnnD4 (50 MHz)
DRAM : 64 MB
FLASH : 8 MB
PC CARD : No card
EEPROM : A Type exist
Ethernet : AUTO-NEGOTIATION
Autoboot Start: 0
[Kernel Image]
Image Address : f0020000
Data Size : 649727 Bytes
Verifying Checksum ... OK
[Ram Disk Image]
Image Address : f06d0000
Data Size : 51916 Bytes
Verifying Checksum ... OK
Linux version 2.4.2_hhl20 (root@localhost.localdomain) (gcc version 2.95.3 2001315 (release/MontaVista)) #249 Wed Feb 26 18:57:29 KST 2003
On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/mtdblock2
RTC Time(mm/dd/yy-hh:mm:ss) : 2/9/20015-15:3:4
Decrementer Frequency = 187500000/60
Calibrating delay loop... 49.86 BogoMIPS
Memory: 62496k available (1204k kernel code, 552k data, 52k init, 0k highmem)
Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes)
Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 4096 (order: 3, 32768 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Starting kswapd v1.8
CPM UART driver version 0.03
ttyS0 on SMC1 at 0x0280, BRG1
ttyS1 on SCC1 at 0x0000, BRG2
CPM interrupt c00ceee8 replacing c00ceee8
pty: 256 Unix98 ptys configured
Oops: kernel access of bad area, sig: 11
NIP: C00CF19C XER: 8000DF7F LR: C00CEA6C SP: C3F95C10 REGS: c3f95b60 TRAP: 0300
MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 0000011C, DSISR: 00000009
TASK = c3f94000[1] 'swapper' Last syscall: 120
last math 00000000 last altivec 00000000
GPR00: 00000000 C3F95C10 C3F94000 C3FFD160 C3F95CE0 C3F95CE0 00000001 00010000
GPR08: C01760B4 00000000 FF0009C0 C0190000 0000000D E0A00000 03FF0E00 007FFF13
GPR16: 00000000 00000001 007FFF00 FFFFFFFF 00001032 03F95CD0 00000002 C016A1A0
GPR24: FF000A00 C3F95CE0 C3FFD160 C0170000 00000005 C017CA80 00000000 0000000E
Call backtrace:
00000001 C00CEA6C C0003904 C0003A30 C0002810 C000FC9C C0183920
C01835F8 C0183668 C0182394 C0181C58 C017D81C C017D8BC C00023A8
C0004E80
Kernel panic: Aiee, killing interrupt handler

In interrupt handler - not syncing
Rebooting in 180 seconds..


**************************************


Thanks
asked Feb 9, 2015 in Console Servers by ArrowLabs New to the Community (0 points)

Please log in or register to answer this question.

1 Answer

0 votes
Have you tried a factory reset?

http://www.digi.com/support/kbase/kbaseresultdetl?id=3491

If this does not work, you will want to contact Digi Tech. Support to pursue repair.
answered Feb 10, 2015 by userid0 Veteran of the Digi Community (2,158 points)
This was correct.  It was being picky on reset.. Had to old down reset button a few different times and ways to finally get it to not just reboot, but to wipe itself back.  Thanks for the help
...