My friend's MK2 suddenly stopped booting. It plays the boot animation but never reaches the status messages before entering the player software. This is a single drive player, no upgrades, running 2.0 final developer and Hijack 464. The only catch, in one of his cars, it's mounted at a 90 degree angle, fascia pointed toward the sky.

Here's the bootlog, showing i2c difficulties, but the (both?) DSP initializes. After the "Partition check", the boot process slows dramatically and "hda: lost interrupt" messages seem to interrupt the log.

Is it a bad DSP like this and this? Or maybe the original hard drive is worn out? I tightened the IDE connectors which didn't help. Any thoughts? Thanks guys.


empeg-car bootstrap v1.00 20000601 (hugo@empeg.com)
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.04
Copying kernel...
Calling linux kernel...
Uncompressing Linux..................................... done, booting the kernel.
Linux version 2.2.17-rmk5-np17-empeg52-hijack-v464 (hijack@rtr.ca) (gcc version 2.95.3 20010315 (release)) #2 Fri Oct 27 01:00:29 EDT 2006
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c0c00000: wrote ffffffff, read e28cc001
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 7, serial number 80000464) 12MB DRAM
Command line: mem=12m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 10952k/12M available (988k code, 20k reserved, 324k data, 4k 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)
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 67706d65 'empg'
Found custom animation at offset 0x9a78c
Tuner: loopback=0, ID=-1
Scheduling custom logo.
empeg display initialised.
empeg dsp audio initialised
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
I2C write failed (fff, d223)
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
I2C write failed (927, 0)
i2c: Failed to receive ACK for data!
i2c_write: device select failed
I2C write failed (8f9, 90d)
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
I2C write failed (8f9, 90d)
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
i2c: Failed to receive ACK for data!
i2c_write: device select failed
I2C write failed (8ef, 800)
i2c: Failed to receive ACK for data!
i2c_write: device select failed
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 d0004c00).
empeg RDS driver initialised
empeg power-pic driver initialised (first boot)
RAM disk driver initialized: 16 RAM disks of 4096K size
empeg single channel IDE
Probing primary interface...
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xaaaa
ide_data_test: wrote 0x5555 read 0x5555
hda: IBM-DARA-212000, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xaaaa
ide_data_test: wrote 0x5555 read 0x5555
hda: IBM-DARA-212000, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xaaaa
ide_data_test: wrote 0x5555 read 0x5555
hda: IBM-DARA-212000, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xaaaa
ide_data_test: wrote 0x5555 read 0x5555
hda: IBM-DARA-212000, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xaaaa
ide_data_test: wrote 0x5555 read 0x5555
hda: IBM-DARA-212000, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xaaaa
ide_data_test: wrote 0x5555 read 0x5555
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 (erik@vt.edu)

SMC9194: SMC91C94(r:9) at 0x4008000 IRQ:7 INTF:TP MEM:6144b MAC 00:02:d7:10:01:d0
Partition check:
hda:hda: lost interrupt
hda: lost interrupt
hda: lost interrupt
hda: lost interrupt
hda1 <hda: lost interrupt
hda5hda: lost interrupt
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...hda: lost interrupt
hda: lost interrupt
hda: lost interrupt
VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=1
hda: lost interrupt
Trying to unmount old root ... okay
Freeing unused kernel memory: 4k inithda: lost interrupt
hda: lost interrupt
hda: lost interrupt
hda: lost interrupt

With a known good drive in the troubled empeg, the boot log looks essentially the same. i2c errors and "hda: lost interrupt".

With the troubled empeg's drive in a known good empeg (MK2a), I received some interesting messages. The first boot, the log showed failing "ide_data_test" messages and the boot ended with "No Hard Disk Found". I removed and replaced the cable, booted, and received this error log. The display showed said: "hda error: hard disk timeout".

Any insight into these i2c and disk errors? Thanks.


empeg-car bootstrap v1.02 20001106 (hugo@empeg.com)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.04Copying kernel...Calling linux kernel...Uncompressing Linux..................................... done, booting the kernel.
Linux version 2.2.17-rmk5-np17-empeg52-hijack-v464 (hijack@rtr.ca) (gcc version 2.95.3 20010315 (release)) #2 Fri Oct 27 01:00:29 EDT 2006
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c1000000: wrote ffffffff, read e28cc001
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 30103002) 16MB DRAM
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15008k/16M available (988k code, 20k reserved, 364k data, 4k 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)
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 '
Found custom animation at offset 0x9877c
Tuner: loopback=0, ID=-1
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 d0004080).
empeg RDS driver initialised
empeg power-pic driver initialised (first boot)
RAM disk driver initialized: 16 RAM disks of 4096K size
empeg single channel IDE
Probing primary interface...
ide_data_test: wrote 0x0000 read 0x0080
ide_data_test: wrote 0xffff read 0x0080
ide_data_test: wrote 0xaaaa read 0x0080
ide_data_test: wrote 0x5555 read 0x0080
ide_data_test: wrote 0x0000 read 0x0080
ide_data_test: wrote 0xffff read 0x0080
ide_data_test: wrote 0xaaaa read 0x0080
ide_data_test: wrote 0x5555 read 0x0080
ide_data_test: wrote 0x0000 read 0x0080
ide_data_test: wrote 0xffff read 0x0080
ide_data_test: wrote 0xaaaa read 0x0082
ide_data_test: wrote 0x5555 read 0x0080
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xaaaa
ide_data_test: wrote 0x5555 read 0x5555
hda: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
hda: IBM-DARA-212000, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xaaaa
ide_data_test: wrote 0x5555 read 0x5555
hda: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
hda: IBM-DARA-212000, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xaaaa
ide_data_test: wrote 0x5555 read 0x5555
hda: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
hda: IBM-DARA-212000, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xaaaa
ide_data_test: wrote 0x5555 read 0x5555
hda: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
hda: IBM-DARA-212000, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xaaaa
ide_data_test: wrote 0x5555 read 0x5555
hda: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
hda: IBM-DARA-212000, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xaaaa
ide_data_test: wrote 0x5555 read 0x5555
hda: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
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 (erik@vt.edu)
SMC9194: SMC91C94(r:9) at 0x4008000 IRQ:7 INTF:TP MEM:6144b MAC 00:02:d7:26:0b:ba
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.
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)Press Ctrl-A to enter pump...hda: status timeout: status=0xffhda: drive not ready for command
ide0: reset: failed
hda: lost interrupt
hda: lost interrupt

Mark, thanks for your diagnostics!

Quote:
on the 44-pin IDE header.

The bad hard drive gave me these same "hda: lost interrupt" messages in the bad empeg and in a known good empeg. Using a known good IDE CABLE, the "bad" drive worked in the good empeg. Maybe I need to retighten the cable headers a bit, or maybe it's frayed from running at a 90 degree angle so often.

Now, to try the bad drive with good cable in bad empeg.

Bad drive, good cable, bad empeg produces the same log as the first one I posted. The cable caused "hda: lost interrupt" messages on my good player, so I'm surprised to see them still here, in the bad player, with the cable replaced. The boot log seems to indicate that it mounted the filesystem, so why the continual stream of "lost interrupt" messages?

The i2c errors remain identical with the working drive. Apparently, this player "just stopped working" one day. Sad.

How about "good drive", "good cable", in "bad empeg". ??

It's essentially the same as the first one I posted. So I guess the poor MK2's cable was hurt, the IDE circuitry has a problem, and the DSP has a problem.

The only odd bit is a resistor soldered in to the right of the IDE header. Maybe this is the fix for the very dim display which Stu applied recently. The MK2 worked like a champ after that job, with its fixed dimmer, new lighting kit, and replaced MK2a knob. Maybe something's worked loose?

Booting with no display or IDE had the same i2c errors. The ide_data_test had some random errors:
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffbf
ide_data_test: wrote 0x5555 read 0xff7f

but eventually ended with everything at 0xffff.

The odd thing is, the ide_data_tests show different errors on different boots. With a good drive in, the tests sarted:
ide_data_test: wrote 0x0000 read 0xff80
ide_data_test: wrote 0xffff read 0xff80
ide_data_test: wrote 0xaaaa read 0xaa80
ide_data_test: wrote 0x5555 read 0x5580

but ended with 0x0000 seeming to fail:
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xaaaa
ide_data_test: wrote 0x5555 read 0x5555

Heck, the best ide_data_tests were with the bad drive, bad cable, bad empeg.... maybe my testing methodology is bad.

Now the bad drive won't work in the good empeg, when it did an hour ago with no problem. Either there's something wrong with my testing methodology or this MK2 got hit with something serious that took out the i2c, ide, and drive. Electrical surge?

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
Now, after using the bad drive in my good player, my good drive is having intermittant problems in my good player. Lag on boot, on screen messages "hda: irq time out" and "hda: status error" (or something like that). It often works, even with an onscreen error, but this is really disconcerting.

So, maybe the bad hard drive, from riding around at a 90 degree angle, has developed a bad condition. Furthermore, that condition damaged the IDE on the bad player, and maybe even the i2c also. Now, the drive has begun to damage my good player from the testing I did.

OR, I'm destroying the IDE cables when I tighten the crimps. I put the IDE connector between a few layers of my shirt and firmly squeeze it in about 10 places with plyers. Yes, the FAQ advises I use some complex tool, but this method has worked for my primary player's biannual loose IDE connector problem.

Or, I'm destroying the motherboard and drive IDE pins. I always seem to bend the few on the end as I remove the cable. Never hurt my main player, but maybe my luck's run out.

Watching my pristine spare empeg lag on boot and give onscreen disk errors is absolutely breaking my heart. I'm going to just walk away from this for now.

Sorry for confusing this thread. Only the first bootlog is relevant, along with Mark's reply. The second bootlog (and Mark's second reply) are from my spare MK2a which I found had lifted IDE header connectors.

So, the MK2 has i2c errors. It also has lost interrupt errors no matter which cable and which drive I use. The IDE header appears to be perfectly attached. Thanks for any feedback or repair suggestions.

I have this player in front of me now and have replaced all the major components (DSP and both PEELs) outside of the processor that are in charge of I2C and the CS lines on the IDE bus, but the lost interrupts and I2C errors persist. I've checked the series resistors in the I2C lines and the oscillation for the DSP and they check out fine.

Any of the Empeg folks have any ideas what else there could be going on here?

Thanks,
Stu

I can't help you, Stu, but I just wanted to chime in and say how cool it is that you're going above and beyond the call of duty here. I can't imagine what it would be like to replace all those surface-mount components. You must have hands that are steady as a rock, nerves of steel, and eyes like an eagle. My hat is off to you.

I just finally fixed a player I have here that had I2C issues. It turned out that the power on pin 65 of the DSP was intermittent, so I resoldered that pin, plus the coil that feeds it (which is way over on the edge of the board past the CPU, and now it plays fine again.

-ml