Dreamboard

HenksatNL · 3. Juli 2008

Hello,

I have a DM800 wich hangs on HD channels after max. 15 minutes.
I`m now testing with DMM experimental image 02 juli, but had the same experiences with DMM latest release.

After changing the bootargs and enabled the bootargs It was possible to made a serial log.
The bootargs I used:
root=/dev/mtdblock3 rootfstype=jffs2 rw console=ttyS0,115200n8

Here is de serial output:

It's now Thu Jul 3 12:26:24 2008
[timer.py] next activation: 1215080884 (in 99995 ms)
It's now Thu Jul 3 12:26:24 2008
[timer.py] next activation: 1215080884 (in 99990 ms)
[EPGC] start cleanloop
[EPGC] stop cleanloop
[EPGC] 3813 bytes for cache used
CPU 0 Unable to handle kernel paging request at virtual address 10008000,
epc ==
c044b3dc, ra == c044b3b0
Oops in arch/mips/mm/fault.c::do_page_fault, line 167[#1]:
Cpu 0
$ 0 : 00000000 10008000 00000000 00001000
$ 4 : c0706ef8 c0700000 00001000 10008000
$ 8 : 10008400 1000001f 00000000 87b8a000
$12 : bfc00600 00000001 1008229c 486ca973
$16 : 0000000c c0700000 0000000d 00000001
$20 : 80309ee0 0000000d b0400780 b0080000
$24 : 00000000 000045c1
$28 : 80308000 80309e10 b0082424 c044b3b0
Hi : fffffff4
Lo : 0000000c
epc : c044b3dc bsettop_irq+0x134/0x194 [bcm7401] Tainted: P
ra : c044b3b0 bsettop_irq+0x108/0x194 [bcm7401]
Status: 10008002 KERNEL EXL
Cause : 80800004
BadVA : 10008000
PrId : 00020000
Modules linked in: zd1211b rt73 fp dreambox_rc2 bcm7401 cu1216mk3 tu1216
alps_bs
be2 stb_proc alps_bsbe1 stv0299 alps_bsbe1_c01a fe_common vfat fat autofs4
usb_s
torage scsi_mod cifs lcd
Process swapper (pid: 0, threadinfo=80308000, task=8030a210)
Stack : 80309e50 80370000 80310000 802d0000 87dab900 00000000 00000000
80047714
80309e50 80370000 80310000 8003008c 803431a0 0000000d 87dab900
fffffffb
80370000 80309ee0 800478a0 8036e238 0000000a 80370000 00000001
8036fd5c
0000000d 00001000 b0400784 80309ee0 00000000 00000012 80005720
80309ee0
10008400 83300000 83040000 830472ac 800030e8 83510000 83040000
8002b97c
...
Call Trace:
[<80047714>] handle_IRQ_event+0x7c/0xf0
[<8003008c>] run_timer_softirq+0x1e8/0x23c
[<800478a0>] __do_IRQ+0x118/0x1a8
[<80005720>] do_IRQ+0x1c/0x34
[<800030e8>] brcm_mips_int2_dispatch+0xf0/0x234
[<8002b97c>] do_softirq+0x8c/0x94
[<80001f48>] brcmIRQ+0x128/0x180
[<80003c04>] r4k_wait+0x0/0xc
[<80360000>] tcp_v4_init+0x44/0x70
[<80005c64>] cpu_idle+0x34/0x58
[<80003c08>] r4k_wait+0x4/0xc
[<8012f54c>] idr_cache_ctor+0x0/0xc
[<803457dc>] start_kernel+0x1d0/0x1e8
[<80345264>] unknown_bootoption+0x0/0x330
[<80345000>] _sinittext+0x0/0x88
[<80345024>] _sinittext+0x24/0x88

Code: ac830024 24a46ef8 90820078 <1440ffe3> 24020001 a0820078 3c03c070
2402
0001 c065e204
Kernel panic - not syncing: Aiee, killing interrupt handler!
<0>Rebooting in 180 seconds..

HenksatNL · 3. Juli 2008

The log above was on NGC HD with CCcam active as cardserver.
This log was on BBC HD without any softcam/cardserver:

It's now Thu Jul 3 13:03:42 2008
[timer.py] next activation: 1215083122 (in 99991 ms)
Reserved instruction in kernel code in arch/mips/kernel/traps.c::do_ri, line 774
[#2]:
Cpu 0
$ 0 : 00000000 10008401 001747b0 00000000
$ 4 : 00000001 80368d28 00000001 80368d28
$ 8 : 001747b1 00000000 00000001 00000000
$12 : 8030a210 80368f68 1008229c 486cb223
$16 : 8030a210 00000000 00000000 80370000
$20 : 80370000 00000000 80309ee0 00000044
$24 : 00000000 0000ed69
$28 : 80308000 80309e10 8030bc40 80030d14
Hi : 00000000
Lo : 00000000
epc : 80030970 check_timer_failed+0x0/0x78 Tainted: P
ra : 80030d14 update_process_times+0x9c/0x15c
Status: 10008402 KERNEL EXL
Cause : 00800028
PrId : 00020000
Modules linked in: zd1211b rt73 fp dreambox_rc2 bcm7401 cu1216mk3 tu1216 alps_bs
be2 stb_proc alps_bsbe1 stv0299 alps_bsbe1_c01a fe_common vfat fat autofs4 usb_s
torage scsi_mod cifs lcd
Process swapper (pid: 0, threadinfo=80308000, task=8030a210)
Stack : 00000000 80370000 80370000 00000044 80370000 ec8e0148 80009ed8 80009ed8
00000000 8036e230 0000000a 80370000 8030bc40 00000000 00000000 00000001
80309ee0 00000044 83040000 83040000 834f0000 80047714 00000000 00000012
b0400780 8002b97c 80343880 00000044 8030bc40 fffffffb 80370000 80309ee0
800478a0 83300000 83040000 830472ac 800030e8 83510000 00808000 83300000
...
Call Trace:
[<80009ed8>] timer_interrupt+0x108/0x224
[<80009ed8>] timer_interrupt+0x108/0x224
[<80047714>] handle_IRQ_event+0x7c/0xf0
[<8002b97c>] do_softirq+0x8c/0x94
[<800478a0>] __do_IRQ+0x118/0x1a8
[<800030e8>] brcm_mips_int2_dispatch+0xf0/0x234
[<80005720>] do_IRQ+0x1c/0x34
[<80001f2c>] brcmIRQ+0x10c/0x180
[<80001f48>] brcmIRQ+0x128/0x180
[<80003c04>] r4k_wait+0x0/0xc
[<80360000>] tcp_v4_init+0x44/0x70
[<80005c64>] cpu_idle+0x34/0x58
[<80003c08>] r4k_wait+0x4/0xc
[<8012f54c>] idr_cache_ctor+0x0/0xc
[<803457dc>] start_kernel+0x1d0/0x1e8
[<80345264>] unknown_bootoption+0x0/0x330
[<80345000>] _sinittext+0x0/0x88
[<80345024>] _sinittext+0x24/0x88

Code: 27bd0038 0800af83 24040001 <27bdffe8> afb00010 afbf0014 3c058037 8ca2
f4ac 00808021

Now I`ve changed the bootargs in:
root=/dev/mtdblock3 rootfstype=jffs2 rw mem=128M console=ttyS0,115200n8

HenksatNL · 3. Juli 2008

Zitat

Original von HenksatNL

Now I`ve changed the bootargs in:
root=/dev/mtdblock3 rootfstype=jffs2 rw mem=128M console=ttyS0,115200n8

This log was from NGC HD:

[EPGC] start cleanloop
[EPGC] stop cleanloop
[EPGC] 323079 bytes for cache used
[EPGC] start cleanloop
[EPGC] stop cleanloop
[EPGC] 323079 bytes for cache used
CPU 0 Unable to handle kernel paging request at virtual address 00200200, epc ==
00200200, ra == 00200200
Oops in arch/mips/mm/fault.c::do_page_fault, line 167[#1]:
Cpu 0
$ 0 : 00000000 10008400 00000000 000000f9
$ 4 : 8036e594 87c710d0 000a7a1d 000a7924
$ 8 : 00000000 00000000 ced70c80 0000009f
$12 : cee64ec0 0000009f 31fe6e00 00000001
$16 : 10008401 802d0000 87c71000 80370000
$20 : 80310000 802d0000 00200200 00100100
$24 : 00000000 2af42aa8
$28 : 80308000 80309e20 834f0000 00200200
Hi : 0000009f
Lo : cee64ec0
epc : 00200200 0x200200 Tainted: P
ra : 00200200 0x200200
Status: 10008402 KERNEL EXL
Cause : 00800008
BadVA : 00200200
PrId : 00020000
Modules linked in: zd1211b rt73 fp dreambox_rc2 bcm7401 cu1216mk3 tu1216 alps_bs
be2 stb_proc alps_bsbe1 stv0299 alps_bsbe1_c01a fe_common vfat fat autofs4 usb_s
torage scsi_mod cifs lcd
Process swapper (pid: 0, threadinfo=80308000, task=8030a210)
Stack : 80309ee0 00000044 8030bc40 80009ed8 00000100 801cccc0 80309e50 8003008c
8030bc40 00000000 00000000 00000001 878e9f30 878e9f30 00000000 8036e238
0000000a 80370000 00000001 8036fd5c 80370000 83040000 8002b830 00000044
8030bc40 fffffffb 80370000 80309ee0 10008400 83300000 83040000 830472ac
83040000 83510000 83040000 8002b97c 83040000 830472ac 83040000 83510000
...
Call Trace:
[<80009ed8>] timer_interrupt+0x108/0x224
[<801cccc0>] rh_report_status+0x0/0x180
[<8003008c>] run_timer_softirq+0x1e8/0x23c
[<8002b830>] __do_softirq+0x8c/0x14c
[<8002b97c>] do_softirq+0x8c/0x94
[<80005728>] do_IRQ+0x24/0x34
[<80001f2c>] brcmIRQ+0x10c/0x180
[<80001f48>] brcmIRQ+0x128/0x180
[<80003c04>] r4k_wait+0x0/0xc
[<80360000>] tcp_v4_init+0x44/0x70
[<80005c64>] cpu_idle+0x34/0x58
[<80003c08>] r4k_wait+0x4/0xc
[<8012f54c>] idr_cache_ctor+0x0/0xc
[<803457dc>] start_kernel+0x1d0/0x1e8
[<80345264>] unknown_bootoption+0x0/0x330
[<80345000>] _sinittext+0x0/0x88
[<80345024>] _sinittext+0x24/0x88

Code: (Bad address in epc)

Kernel panic - not syncing: Aiee, killing interrupt handler!
<0>Rebooting in 180 seconds..

neuweiler · 11. Juli 2008

Hiya,

I experience exactly the same problem with two DM800S from the latest delivery (last week). The box freezes on any HD channel after about 15min (also with orig image and no emu), sound sometimes goes on, sometimes automatic reboot aber 5min. Tuner is getting very hot (45 deg cels on case -> hotter inside). Tried many different things (incl. active cooling with fan) and now I was thinking about returning the box. But seeing your posts here with kernel stops gives me hopes that it might be a software problem.
Did you get any response from dream yet ?
There's a related post: DM800 Crashing on BBCHD

floh · 11. Juli 2008

If it was a Software-Problem, it would happen with every 800. This ist not the case.
Mine is working fine. (At least with the latest driver)

But before returning the Box you should make shure you tried the latest drivers.

neuweiler · 11. Juli 2008

floh: with the release or the latest cvs image ?

Well, the stack trace shows page faults as the cause of a kernel panic. Either it's a problem in the kernel or a driver or a somewhat different hardware was used for the units that cause problems. Maybe a different memory manufacturer? Maybe our RAMs are not that heat resistant as others ?

In other counries (Netherlands, Sweden) there are also many problems reported. Looks like their fix was installing a fan to cool the unit. I did the same and got only one crash since then - looks more stable. But to be honest, if the heat really was the cause, I'd be far from happy !

floh · 11. Juli 2008

If you want the most recent drivers try one from here

neuweiler · 12. Juli 2008

I opened a ticket at DMM tonight and already received a reply. Need to send in the box for a warranty repair. They don't suspect a software problem.
I was impressed by the quick response from DMM. I suggest you also contact their support directly if you experience these problems.

postbus24 · 16. Juli 2008

same problem over here, box hangs on a HD channel after some time. But I want to make sure I tried everything before I conclude it might be a hardware problem.

these are my hardware details:
Product DM800
Bootloader Version Build #61, built 20080521
Board revision 0
Serial Number 861313000012771
MAC Address 00:09:34:27:b9:3a
Production Date 2008/06/13

Zitat

Originally posted by floh
If you want the most recent drivers try one from here

Are these drivers the latest 'official' drivers ? In other words, if I use these and my problem is not solved -> not good

HenksatNL: I suppose you use hyperterminal on the serial port for your log trace but how and where do you change the bootargs ?

FeRgY · 16. Juli 2008

Zitat

Originally posted by postbus24
HenksatNL: I suppose you use hyperterminal on the serial port for your log trace but how and where do you change the bootargs ?

by pressing backspace on begin of first message in hyperterm or minicom window and just to type:

Code

root=/dev/mtdblock3 rootfstype=jffs2 [B]rw mem=128M[/B] console=ttyS0,115200n8

instead of:

Code

root=/dev/mtdblock3 rootfstype=jffs2 [B]rw[/B] console=ttyS0,115200n8

EDIT: sorry no bold function enabled in code, but between [Bold] and [/b] is right command

postbus24 · 17. Juli 2008

Zitat

by pressing backspace on begin of first message in hyperterm or minicom

doesn't do anything in winXP hyperterminal.
no mather how hard i keep jamming this key ,It just continues booting evry time ....

anny suggestions

FeRgY · 18. Juli 2008

Telnet the following :-

Code

init 4

Code

killall -9 enigma2

Code

enigma2>/tmp/e.log 2>&1 &

after that attach log file from Your /tmp folder here
Cheers

postbus24 · 21. Juli 2008

Since its only E2 log, it is not very helpful I think:

Zitat

[EPGC] start cleanloop
[EPGC] stop cleanloop
[EPGC] 5375 bytes for cache used
[EPGC] start cleanloop
[EPGC] stop cleanloop
[EPGC] 5375 bytes for cache used
It's now Mon Jul 21 22:15:12 2008
[timer.py] next activation: 1216671412 (in 99992 ms)
It's now Mon Jul 21 22:15:12 2008
[timer.py] next activation: 1216671412 (in 99984 ms)
[EPGC] start cleanloop
[EPGC] stop cleanloop
[EPGC] 5375 bytes for cache used

Alles anzeigen

FeRgY · 21. Juli 2008

It is, but if You leave until box hang... You will not be able to get log because tmp will probably be deleted.
So, terminal thing back.

postbus24 · 22. Juli 2008

Zitat

Originally posted by FeRgY
It is, but if You leave until box hang... You will not be able to get log because tmp will probably be deleted.
So, terminal thing back.

was way ahead of you log was written to /etc/e2.log
As you can see in the trace of HenksatNL it is a 'kernel' issue so in the end it makes sense that e2 is not aware and showing anything unusual.

Receiver is back to supplier since this moring, hopefully it will be repaired soon

FeRgY · 23. Juli 2008

Good luck

nvandijk · 30. Juli 2008

My DM800 also hangs after about 10 minutes of watching HD channels.
Seems te be heating problemen. I tested it simple by putting my box on it's side ( with the oled screen upwards ) and this seems te give it just enough cooling to not stop working. Watched BBC HD for more than 2 hours and it still worked. Left it on all night and in the morning it was still working.

Just to let you know.

FeRgY · 30. Juli 2008

Get a silicon paste and an cooler from old graphic card ( what pass on chip ) , put paste, press cooler and VOILA! Your box working without problem and/or sending back to dmm

postbus24 · 5. August 2008

Zitat

Originally posted by FeRgY
Get a silicon paste and an cooler from old graphic card ( what pass on chip ) , put paste, press cooler and VOILA! Your box working without problem and/or sending back to dmm

For me that is the same solution as buying an other type/brand receiver

BTW can you please explain this command to me ?

Code

enigma2>/tmp/e.log 2>&1 &

More specific what does the '2>&1 &' stands for ?

thanx in advance =)

postbus24 · 5. August 2008

Zitat
Originally posted by postbus24
Code
enigma2>/tmp/e.log 2>&1 &
More specific what does the '2>&1 &' stands for ?

thanx in advance =)
Alles anzeigen

I got it ! write both STDOUT and STDERR to /tmp/e.log