which chip is faulty?

[JOCKYW2001]

I bought a used Sagem 1xI satbox some weeks ago and unfortunately it doesn't work properly. After some time there are picture glitches and then it suddenly reboots. I reported that in another thread:
https://tuxbox-cvs.sourceforge.net/foru ... hp?t=29961

By exchanging different parts (powersupply, frontpanel, etc.) with parts from my Sagem cablebox I can conclude that the problem must be on the mainboard or in the tunermodule. In the bootlog following error is reported short before it crashes:

Code: Alles auswählen

avia_av: status timeout - chip not ready for new command
avia_av: microcode verify: 25372 errors.
avia_av: timeout waiting for decoder init to complete. (00000000)
avia_av: wakeup error
Oops: kernel access of bad area, sig: 11
NIP: C38B0120 XER: 00000000 LR: C38B0110 SP: C15F5D20 REGS: c15f5c70 TRAP: 0300
   Not tainted
MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 00000006, DSISR: 00000FAB
....

Any hw experts who can tell which chip is at fault?
Can this be caused by an improper debugmode? Should I disable and re-enable debugmode?
Do you know any repairservice who could fix this for a reasonable price?
If not repairable, what could be a reasonable price to sell a defect dbox2 on eBay?

Thx and Happy Easter,
JockyW

[DieMade]

Looks like an defective AVIA600 and/or it's RAM.

[JOCKYW2001]

Looks like an defective AVIA600 and/or it's RAM.

Thanks.
Do you mean the RAM inside the Avia600?
Would it help if I put some kind of cooler on the Avia600?

[DieMade]

The AVIA600 has external RAM placed near to it. The Chip is supposed to run without any extra cooling.

[JOCKYW2001]

I'm trying to determine if it is the Avia600 or the RAM chip which sits beside it. In a bootlog this afternoon I found this:
avia_av: status timeout - chip didn't accept command 0x231
avia_av_event: $Id: avia_av_event.c,v 1.11 2003/10/26 16:32:51 obi Exp $

Is that also an Avia600 fault? Or could it be the RAM as well?

[Npq]

You'll probably need to replace one part to make sure, it could be the RAM itself that's giving trouble (the ucode verification above talks about several errors) but it could also be the bus interface to the RAM.

The Avia-RAM is not part of the main memory, it's a RAM of its own with a bus of its own, you can access it through an 8-Bit interface.

I think you can write to it through the /proc-Interface. Check the driver about the write-access, I'm not 100% on this at the moment.

[JOCKYW2001]

See http://forum.tuxbox-cvs.sourceforge.net ... hp?t=29961
My Sagem is cured after disabling debug mode! Can anyone explain that or is it plain luck. After all I didn't use it in the past 2 months.