[leaf-wisp] Boot problem in "Loading modules" with Kernel panic

Patrick Spousta <[email protected]> Tue, 12 Oct 2004 06:43:46 +0200
Newsgroups gmane.linux.leaf.wisp-dist
Message-ID <[email protected]>
Hi,
I have built last release of WISP (patch 33) without any modification of 
sources. During boot I get this messages (see bottom). I'm compiling od 
Debian Woody (stable) Linux

gcc 2.95
glibc 2.2.5-11.5

I'm using .bin image on CF card. When I use prebuilt image (release or 
patch 30) from your website, everthing is ok. I tried to use WISP on 
WRAP board from PC Engines with SC1100 CPU (x86 compat.)

Can you help me?

Thanks
Patrick

**************************************************************************
Loading modules...
Using /boot/lib/modules/mtdcore.o
Using /boot/lib/modules/doc2000.o
insmod: unresolved symbol nand_flash_ids
insmod: unresolved symbol doc_decode_ecc
insmod: uPossible DiskOnChip with unknown ChipID FF found at 0xc8000
nresolved symbolPossible DiskOnChip with unknown ChipID FF found at 0xca000
Possible DiskOnChip with unknown ChipID FF found at 0xcc000

Using /boot/libPossible DiskOnChip with unknown ChipID FF found at 0xce000
/modules/docecc.Possible DiskOnChip with unknown ChipID FF found at 0xd0000
o
Using /boot/lPossible DiskOnChip with unknown ChipID FF found at 0xd2000
ib/modules/docprPossible DiskOnChip with unknown ChipID FF found at 0xd4000
obe.o
Possible DiskOnChip with unknown ChipID FF found at 0xd6000
Possible DiskOnChip with unknown ChipID FF found at 0xd8000
Possible DiskOnChip with unknown ChipID FF found at 0xda000
Possible DiskOnChip with unknown ChipID FF found at 0xdc000
Possible DiskOnChip with unknown ChipID FF found at 0xde000
Possible DiskOnChip with unknown ChipID FF found at 0xe0000
Possible DiskOnChip with unknown ChipID FF found at 0xe2000
Possible DiskOnChip with unknown ChipID FF found at 0xe4000
Possible DiskOnChip with unknown ChipID FF found at 0xe6000
Possible DiskOnChip with unknown ChipID FF found at 0xe8000
Possible DiskOnChip with unknown ChipID FF found at 0xea000
Possible DiskOnChip with unknown ChipID FF found at 0xec000
Possible DiskOnChip with unknown ChipID FF found at 0xee000
No recognised DiskOnChip devices found
Using /boot/lib/modules/nftl.o
NFTL driver: nftlcore.c $Revision: 1.87 $, nftlmount.c $Revision: 1.31 $
Using /boot/lib/modules/ide-core.o
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Using /boot/lib/modules/ide-disk.o
Using /boot/lib/modules/ide-detect.o
hda: Hitachi XX.V.3.3.0.0, CFA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Using /boot/lib/modules/cramfs.o
Making a 8M TMPFS filesystem...
Pivoting...
Generating default dirs...
Generating /tmp & /var/log files ...
Generating /dev...
hda: attached ide-disk driver.
general protection fault: 0000
CPU:    0
EIP:    0010:[<c01127b6>]    Not tainted
EFLAGS: 00010086
eax: c3e4a000   ebx: c3e4bbf8   ecx: ffffffff   edx: c3e4bbf8
esi: c3e4bc20   edi: ffffffff   ebp: c3e4bc00   esp: c3e4bbd8
ds: 0018   es: 0018   ss: 0018
Process mount (pid: 204, stackpage=c3e4b000)
Stack: c3f1c060 00000246 00000000 c3e4a000 00000000 00000000 00000001 
c3e4a000
        c3e4bc28 ffffffff c3f1c060 c4825608 c482ef60 c3f1c060 00000000 
c3e4bc24
        c3e4bc24 c3e4a000 00000000 c3e4bc24 c3e4bc24 c3e4bbf8 c3e4bcf0 
c3e4bce8
Call Trace:    [<c4825608>] [<c482ef60>] [<c481e188>] [<c482ef50>] 
[<c482ef88>]
   [<c482ef88>] [<c482ef50>] [<c481e1a6>] [<c482ef50>] [<c4834482>] 
[<c482ef50>]
   [<c481d6a0>] [<c482ef50>] [<c48345c0>] [<c482ef50>] [<c482ef50>] 
[<c482eea0>]
   [<c483555a>] [<c482ef50>] [<c482ef50>] [<c48358c6>] [<c482ef50>] 
[<c48362cc>]
   [<c481fe93>] [<c482ef50>] [<c481ff2c>] [<c013736a>] [<c0137498>] 
[<c01362b8>]
   [<c01459e6>] [<c013658b>] [<c01468f9>] [<c0146bab>] [<c0146a1c>] 
[<c0146f34>]
   [<c0108843>]

Code: 89 11 89 c3 8d b6 00 00 00 00 c7 03 02 00 00 00 fb e8 94 fa
  Segmentation fauhda: task_no_data_intr: status=0x51lt
  { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
Unable to handle kernel NULL pointer dereference at virtual address 00000001
  printing eip:
c01126d8
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c01126d8>]    Not tainted
EFLAGS: 00010097
eax: c3e4bc28   ebx: c3e4bc24   ecx: 00000001   edx: c3e4bc24
esi: c3e4bc20   edi: 00000086   ebp: c3f97ea8   esp: c3f97e94
ds: 0018   es: 0018   ss: 0018
Process linuxrc (pid: 1, stackpage=c3f97000)
Stack: c3e4bc50 c3e4bc20 c3e4bc50 00000001 c3e4bc24 c482ef50 c0187b84 
00000297
        c482eea0 c48243d2 c3e4bc50 00000004 00000051 00000051 c3e4bc50 
c482ef50
        00000051 c4834234 c482ef50 00000051 00000004 c482eea0 00000051 
c3e7026c
Call Trace:    [<c482ef50>] [<c0187b84>] [<c482eea0>] [<c48243d2>] 
[<c482ef50>]
   [<c4834234>] [<c482ef50>] [<c482eea0>] [<c0111563>] [<c0111400>] 
[<c01428bf>]
   [<c482eea0>] [<c482ef50>] [<c481d6ec>] [<c482ef50>] [<c482ca9f>] 
[<c482ef50>]
   [<c482eea0>] [<c48253ea>] [<c482ef50>] [<c481d6a0>] [<c0109caf>] 
[<c0109e2e>]
   [<c010c048>]

Code: 8b 01 a8 03 74 53 31 c0 9c 5e fa c7 01 00 00 00 00 83 79 3c
  <0>Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing




-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl