Unoffical empeg BBS

Quick Links: Empeg FAQ | RioCar.Org | Hijack | BigDisk Builder | jEmplode | emphatic
Repairs: Repairs

Topic Options
#59086 - 15/01/2002 07:32 Infinite loop on bootup (log attached)
trevorp
member

Registered: 08/06/2000
Posts: 144
Loc: Ft Lauderdale, FL
Good morning,
I'm posting on behalf of one of the people in my office. He just got a new 12GB Rio. After synching about 3.5GB, he got the following error message: "warning.. Database did not synchronize"

We have tried flashing between 1.03 and 2.0b7, both with the same result. I'm not sure what the memory violation mentioned below is...

Below is the boot log. It repeats infinitely:

empeg-car bootstrap v1.02 20001106 ([email protected])
If there is anyone present who wants to upgrade the flash, let them speak now,
or forever hold their peace...it seems not. Let fly the Penguins of Linux!

e000 v1.03
Copying kernel...
Calling linux kernel...
Uncompressing Linux................................... done, booting the kernel.

Linux version 2.2.14-rmk5-np17-empeg43 ([email protected]) (gcc versi
on 2.95.2 19991024 (release)) #214 Sat Jun 23 16:38:57 BST 2001
Processor: Intel StrongARM-1100 revision 11
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 120001127)
Command line: mem=16m temp=36
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15064k/16M available (960k code, 20k reserved, 332k data, 8k init)
Dentry hash table entries: 2048 (order 2, 16k)
Buffer cache hash table entries: 16384 (order 4, 64k)
Page cache hash table entries: 4096 (order 2, 16k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 16384 bhash 16384)
IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
Linux-IrDA: IrCOMM protocol ( revision:Tue May 18 03:11:39 1999 )
ircomm_tty: virtual tty driver for IrCOMM ( revision:Wed May 26 00:49:11 1999 )
Starting kswapd v 1.5
SA1100 serial driver version 4.27 with no serial options enabled
ttyS00 at 0xf8010000 (irq = 15) is a SA1100 UART
ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UART
ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UART
Signature is 206f6972 'rio '
empeg display initialised.
empeg dsp audio initialised
empeg dsp mixer initialised
empeg dsp initialised
empeg audio-in initialised, CS4231A revision a0
empeg remote control/panel button initialised.
empeg usb initialised, PDIUSBD12 id 1012
empeg state support initialised 0089/88c1 (save to d0004980).
empeg RDS driver initialised
empeg power-pic driver initialised
RAM disk driver initialized: 16 RAM disks of 4096K size
empeg single channel IDE
Probing primary interface...
hda: IBM-DARA-212000, ATA DISK drive
hda: IBM-DARA-212000, ATA DISK drive
hda: IBM-DARA-212000, ATA DISK drive
hda: IBM-DARA-212000, ATA DISK drive
hda: IBM-DARA-212000, ATA DISK drive
hda: IBM-DARA-212000, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: IBM-DARA-212000, 11513MB w/418kB Cache, CHS=23392/16/63
empeg-flash driver initialized
smc chip id/revision 0x3349
smc9194.c:v0.12 03/06/96 by Erik Stahlman ([email protected])

SMC9194: SMC91C94(r:9) at 0x4008000 IRQ:7 INTF:TP MEM:6144b MAC 00:02:d7:18:04:6
7
Partition check:
hda: hda1 < hda5 hda6 > hda2 hda3 hda4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=1
Trying to unmount old root ... okay
Freeing unused kernel memory: 8k initplayer: memory violation at pc=0x0209b844,
lr=0x0209b7f4 (bad address=0x0b118da1, code 2)
pc : [<0209b844>] lr : [<0209b7f4>]
sp : bffffd70 ip : bffffd90 fp : bffffd8c
r10: 02114bf0 r9 : 0211351c r8 : bffffe90
r7 : 0b118d9d r6 : 0211294c r5 : 02118d99 r4 : 09000004
r3 : 00000000 r2 : 09000004 r1 : 02118d99 r0 : 0211294c
Flags: nZCv IRQs on FIQs on Mode USER_32 Segment user
Control: C0EE517D Table: C0EE517D DAC: 00000015
Function entered at [<0209b824>] from [<0209b7f4>]
r7 = BFFFFE94 r6 = 021191E8 r5 = 02118D99 r4 = 0211294C
Function entered at [<0209b74c>] from [<02083adc>]
r5 = 021191D8 r4 = 00000001
Function entered at [<02083a60>] from [<020734ac>]
r10 = 02118DA1 r9 = 0211351C r8 = BFFFFE90 r7 = BFFFFE94
r6 = 021191E8 r5 = 021191D8 r4 = 00000001
Function entered at [<020722b8>] from [<02008b20>]
r10 = 02008A24 r9 = 00000000 r8 = 020D9134 r7 = 00000000
r6 = 020000C0 r5 = BFFFFF64 r4 = 02114B8C
Function entered at [<02008af0>] from [<02008c98>]
r4 = 02114B8C
Function entered at [<02008c80>] from [<020cbe34>]
Function entered at [<020cbe10>] from [<020000d4>]
r4 = 00000001
Function entered at [<020000c0>] from [<020878d4>]
Function entered at [<02087810>] from [<02000104>]
r10 = 00000000 r8 = 00000000 r7 = 00000000 r6 = 00000000
r5 = 00000000 r4 = 00000000
player: memory violation at pc=0x0209b844, lr=0x0209b7f4 (bad address=0x0b118da1
, code 2)
pc : [<0209b844>] lr : [<0209b7f4>]
sp : bffffd70 ip : bffffd90 fp : bffffd8c
r10: 02114bf0 r9 : 0211351c r8 : bffffe90
r7 : 0b118d9d r6 : 0211294c r5 : 02118d99 r4 : 09000004
r3 : 00000000 r2 : 09000004 r1 : 02118d99 r0 : 0211294c
Flags: nZCv IRQs on FIQs on Mode USER_32 Segment user
Control: C0EE517D Table: C0EE517D DAC: 00000015
Function entered at [<0209b824>] from [<0209b7f4>]
r7 = BFFFFE94 r6 = 021191E8 r5 = 02118D99 r4 = 0211294C
Function entered at [<0209b74c>] from [<02083adc>]
r5 = 021191D8 r4 = 00000001
Function entered at [<02083a60>] from [<020734ac>]
r10 = 02118DA1 r9 = 0211351C r8 = BFFFFE90 r7 = BFFFFE94
r6 = 021191E8 r5 = 021191D8 r4 = 00000001
Function entered at [<020722b8>] from [<02008b20>]
r10 = 02008A24 r9 = 00000000 r8 = 020D9134 r7 = 00000000
r6 = 020000C0 r5 = BFFFFF64 r4 = 02114B8C
Function entered at [<02008af0>] from [<02008c98>]
r4 = 02114B8C
Function entered at [<02008c80>] from [<020cbe34>]
Function entered at [<020cbe10>] from [<020000d4>]
r4 = 00000001
Function entered at [<020000c0>] from [<020878d4>]
Function entered at [<02087810>] from [<02000104>]
r10 = 00000000 r8 = 00000000 r7 = 00000000 r6 = 00000000
r5 = 00000000 r4 = 00000000
player: memory violation at pc=0x0209b844, lr=0x0209b7f4 (bad address=0x0b118da1
, code 2)
pc : [<0209b844>] lr : [<0209b7f4>]
sp : bffffd70 ip : bffffd90 fp : bffffd8c
r10: 02114bf0 r9 : 0211351c r8 : bffffe90
r7 : 0b118d9d r6 : 0211294c r5 : 02118d99 r4 : 09000004
r3 : 00000000 r2 : 09000004 r1 : 02118d99 r0 : 0211294c
Flags: nZCv IRQs on FIQs on Mode USER_32 Segment user
Control: C0EE517D Table: C0EE517D DAC: 00000015
Function entered at [<0209b824>] from [<0209b7f4>]
r7 = BFFFFE94 r6 = 021191E8 r5 = 02118D99 r4 = 0211294C
Function entered at [<0209b74c>] from [<02083adc>]
r5 = 021191D8 r4 = 00000001
Function entered at [<02083a60>] from [<020734ac>]
r10 = 02118DA1 r9 = 0211351C r8 = BFFFFE90 r7 = BFFFFE94
r6 = 021191E8 r5 = 021191D8 r4 = 00000001
Function entered at [<020722b8>] from [<02008b20>]
r10 = 02008A24 r9 = 00000000 r8 = 020D9134 r7 = 00000000
r6 = 020000C0 r5 = BFFFFF64 r4 = 02114B8C
Function entered at [<02008af0>] from [<02008c98>]
r4 = 02114B8C
Function entered at [<02008c80>] from [<020cbe34>]
Function entered at [<020cbe10>] from [<020000d4>]
r4 = 00000001
Function entered at [<020000c0>] from [<020878d4>]
Function entered at [<02087810>] from [<02000104>]
r10 = 00000000 r8 = 00000000 r7 = 00000000 r6 = 00000000
r5 = 00000000 r4 = 00000000
Respawning too fast, next cycle will ignore flash
Respawning too quickly, ignoring flash settings
player: memory violation at pc=0x0209b844, lr=0x0209b7f4 (bad address=0x0b118da1
, code 2)
pc : [<0209b844>] lr : [<0209b7f4>]
sp : bffffd60 ip : bffffd80 fp : bffffd7c
r10: 02114bf0 r9 : 0211351c r8 : bffffe80
r7 : 0b118d9d r6 : 0211294c r5 : 02118d99 r4 : 09000004
r3 : 00000000 r2 : 09000004 r1 : 02118d99 r0 : 0211294c
Flags: nZCv IRQs on FIQs on Mode USER_32 Segment user
Control: C0EE517D Table: C0EE517D DAC: 00000015
Function entered at [<0209b824>] from [<0209b7f4>]
r7 = BFFFFE84 r6 = 021191E8 r5 = 02118D99 r4 = 0211294C
Function entered at [<0209b74c>] from [<02083adc>]
r5 = 021191D8 r4 = 00000001
Function entered at [<02083a60>] from [<020734ac>]
r10 = 02118DA1 r9 = 0211351C r8 = BFFFFE80 r7 = BFFFFE84
r6 = 021191E8 r5 = 021191D8 r4 = 00000001
Function entered at [<020722b8>] from [<02008b20>]
r10 = 02008A24 r9 = 00000000 r8 = 020D9134 r7 = 00000000
r6 = 020000C0 r5 = BFFFFF54 r4 = 02114B8C
Function entered at [<02008af0>] from [<02008c98>]
r4 = 02114B8C
Function entered at [<02008c80>] from [<020cbe34>]
Function entered at [<020cbe10>] from [<020000d4>]
r4 = 00000002
Function entered at [<020000c0>] from [<020878d4>]
Function entered at [<02087810>] from [<02000104>]
r10 = 00000000 r8 = 00000000 r7 = 00000000 r6 = 00000000
r5 = 00000000 r4 = 00000000
Still respawning too fast, rebooting...
Restarting system.
_________________________
-Trevor

-----
Mk 2, Green 12GB, Tuner, 2.0b11, 080000349

Top
#59087 - 15/01/2002 13:17 Re: Infinite loop on bootup (log attached) [Re: trevorp]
trevorp
member

Registered: 08/06/2000
Posts: 144
Loc: Ft Lauderdale, FL
Well, installing the builder image, and then re-flashing to a consumer image seems to have done the trick.
_________________________
-Trevor

-----
Mk 2, Green 12GB, Tuner, 2.0b11, 080000349

Top
#59088 - 15/01/2002 13:55 Re: Infinite loop on bootup (log attached) [Re: trevorp]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31583
Loc: Seattle, WA
You probably shouldn't have needed to do the builder image. That erases the hard disk completely. That's a last-resort thing that you shouldn't need to do.

There are ways to repair the database. But most importantly, whenever you run into trouble with one of the betas (I'm assuming you were running 2.0 beta7), you should remember to always try downgrading to the stable final-release 1.03. Betas are named "beta" for a reason.
_________________________
Tony Fabris

Top
#59089 - 15/01/2002 13:58 Re: Infinite loop on bootup (log attached) [Re: tfabris]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31583
Loc: Seattle, WA
Okay, I re-checked the log file and it seems he was on 1.03.

Okay, I'd worry about hardware problems at this point. Try the ctrl-T memory test and keep an eye out for disk cable problems.
_________________________
Tony Fabris

Top
#59090 - 15/01/2002 14:57 Re: Infinite loop on bootup (log attached) [Re: tfabris]
trevorp
member

Registered: 08/06/2000
Posts: 144
Loc: Ft Lauderdale, FL
Thanks for the response Tony. We ran the builder image, as he had only just dumped the songs on it, and had them all set up to dump again, so it was no big deal. He was worried about his new toy not working, so we just did the most expedient thing.

I'll try the ^T test tomorrow.
_________________________
-Trevor

-----
Mk 2, Green 12GB, Tuner, 2.0b11, 080000349

Top