Hilfe!!!! Meine Box bootet nicht. Kernel Panic!

Anlaufschwierigkeiten? Was ist was? Worum geht's?
mr_jackdaniel

Hilfe!!!! Meine Box bootet nicht. Kernel Panic!

Beitrag von mr_jackdaniel »

Hallo!

ALARM ROT!


Habe gerade das neue 1.8.1.5 aufgespielt, jetzt bleibt die Box hängen.

Wie kann ich die Kiste retten?

Hier die Logdatei:

ÿdebug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: BMon V1.0 mID 01
debug: feID dd gtxID 0b
debug: fpID 5a dsID 01-ff.e0.19.07.00.00-60
debug: HWrev X5 SWrev 0.81
debug: B/Ex/Fl(MB) 32/00/08

WATCHDOG reset enabled

dbox2:root> debug:
BOOTP/TFTP bootstrap loader (v0.3)
debug:
debug: Transmitting BOOTP request via broadcast
debug: Given up BOOTP/TFTP boot

boot net failed

Flash-FS bootstrap loader (v1.5)

Found Flash-FS superblock version 3.1
Found file /root/platform/nokia-dbox2/kernel/os in Flash-FS
debug: Got Block #0032
debug: Got Block #0004
debug: Got Block #0008
debug: Got Block #0012
debug: Got Block #0016
debug: Got Block #0020
debug: Got Block #0024
debug: Got Block #0028
debug: Got Block #0032



will verify ELF image, start= 0x800000, size= 152952

verify sig: 263
Branching to 0x40000


U-Boot 1.1.1 (TuxBox) (Jun 26 2004 - 23:20:18)

CPU: PPC823ZTnnA at 67.200 MHz: 2 kB I-Cache 1 kB D-Cache
*** Warning: CPU Core has Silicon Bugs -- Check the Errata ***
Board: DBOX2, Nokia, BMon V1.0
Watchdog enabled
I2C: ready
DRAM: 32 MB

FLASH: 8 MB
Scanning JFFS2 FS: | / - \ done. find_inode failed for name=tuxbox load: Failed to find inode FB: ready
LCD: ready
In: serial
Out: serial
Err: serial
Net: SCC ETHERNET
Scanning JFFS2 FS: | / - \ done. find_inode failed for name=tuxbox load: Failed to find inode ready - can't find logo in flash
Scanning JFFS2 FS: | / - \ done. find_inode failed for name=tuxbox load: Failed to find inode can't find logo in flash

Options:
1: Console on null
2: Console on ttyS0
3: Console on framebuffer
Select option (1-3), other keys to stop autoboot: 1 0
### FS (jffs2) loading 'vmlinuz' to 0x100000
Scanning JFFS2 FS: . | / done. ### FS load complete: 610192 bytes loaded to 0x100000
...............................................................
Un-Protected 63 sectors

## Booting image at 00100000 ...
Image Name: dbox2
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 610128 Bytes = 595.8 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.4.25-dbox2 (mogway@yadi.org) (gcc version 3.3.3) #5 So Jun 27 12:21:57 CEST 2004

On node 0 totalpages: 8192

zone(0): 8192 pages.

zone(1): 0 pages.

zone(2): 0 pages.

Kernel command line: console=ttyS0 root=/dev/mtdblock3 rootfstype=squashfs

Decrementer Frequency = 252000000/60

m8xx_wdt: active wdt found (SWTC: 0xFFFF, SWP: 0x1)

m8xx_wdt: keep-alive trigger installed (PITC: 0x1000)

Console: colour dummy device 80x25

Calibrating delay loop... 66.96 BogoMIPS

Memory: 30908k available (1032k kernel code, 368k data, 60k init, 0k highmem)

Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)

Inode cache hash table entries: 2048 (order: 2, 16384 bytes)

Mount cache hash table entries: 512 (order: 0, 4096 bytes)

Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)

Page-cache hash table entries: 8192 (order: 3, 32768 bytes)

POSIX conformance testing by UNIFIX

Linux NET4.0 for Linux 2.4

Based upon Swansea University Computer Society NET3.039

Initializing RT netlink socket

Starting kswapd

devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)

devfs: boot_options: 0x1

JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.

i2c-core.o: i2c core module version 2.6.1 (20010830)

i2c-dev.o: i2c /dev entries driver module version 2.6.1 (20010830)

CPM UART driver version 0.04

ttyS0 at 0x0280 is on SMC1 using BRGttyS1 at 0x0380 is on SMC2 using BRG2

pty: 256 Unix98 ptys configured

eth0: CPM ENET Version 0.2.dbox2 on SCC2, 00:50:9c:1e:33:66

D-Box 2 flash driver (size->0x800000 mem->0x10000000)

D-Box 2 flash memory: Found 2 x16 devices at 0x0 in 32-bit mode

Intel/Sharp Extended Query Table at 0x0035

cfi_cmdset_0001: Erase suspend on write enabled

Using word write method

Creating 7 MTD partitions on "D-Box 2 flash memory":

0x00000000-0x00020000 : "BR bootloader"

0x00020000-0x00040000 : "flfs (u-boot)"

0x00040000-0x000e0000 : "kernel (jffs2)"

0x000e0000-0x006a0000 : "root (squashfs)"

0x006a0000-0x00800000 : "var (jffs2)"

0x00020000-0x00800000 : "flash without bootloader"

0x00000000-0x00800000 : "complete flash"

Linux video capture interface: v1.00

mice: PS/2 mouse device common for all mice

NET4: Linux TCP/IP 1.0 for NET4.0

IP Protocols: ICMP, UDP, TCP

IP: routing cache hash table of 512 buckets, 4Kbytes

TCP: Hash tables configured (established 2048 bind 4096)

NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.

Oops: kernel access of bad area, sig: 11

NIP: C0046CE0 XER: C000047F LR: C0046D64 SP: C01EDCC0 REGS: c01edc10 TRAP: 0300 Not tainted

MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11

DAR: 00000003, DSISR: 00000BC9

TASK = c01ec000[1] 'swapper' Last syscall: 120

last math 00000000 last altivec 00000000

GPR00: C1EFE070 C01EDCC0 C01EC000 C0107240 C0108F90 0000028D C01FA690 C01FA688

GPR08: C01FA678 FFFFFFFF C01FA670 C0120000 53305053 00031B58 01FFB500 00000001

GPR16: FFFFFFFF 007FFF00 01FF5A64 00000000 00000001 007FFEC0 C0130000 C01EDE40

GPR24: C1F12150 00001F03 00000001 C1F68400 00001F03 C01FA660 C01FA690 C1EFE060

Call backtrace:

C00273F0 C0046D64 C006E3F8 C0037168 C0037564 C004C024 C004C3A4

C004C8DC C012E9A8 C00024D0 C00022B4 C0004D20

Kernel panic: Attempted to kill init!

<0>Rebooting in 180 seconds..


Danke für Tips,

Wolfgang
Spooky
Einsteiger
Einsteiger
Beiträge: 338
Registriert: Sonntag 24. Februar 2002, 10:43

Beitrag von Spooky »

Wenn die Box nach herausziehen und wieder reinstecken des Stromsteckers die selbe Meldung bringt, hilft nur ein neues Image aufspielen. Nach Deinem log ist entweder beim Flashen etwas schief gegangen oder das verwendete Image ist an sich unbrauchbar.

Gruß
Spooky
mr_jackdaniel

Beitrag von mr_jackdaniel »

Hallo Spooky,

habe die 1.8.1.5 erneut aufgespielt, gleicher Fehler. Auch wenn ich von einem anderen Mirror sauge, kommt der gleiche Fehler.

Habe jetzt die 1.8.1.4 genommen, die klappt einwandfrei.


Schönen Abend noch,

Wolfgang