Jump to content


Photo

Edision osmini(dvb-s2+dvb-t2/c) crashed


  • Please log in to reply
33 replies to this topic

Re: Edision osmini(dvb-s2+dvb-t2/c) crashed #21 Cofybreak

  • Senior Member
  • 115 posts

0
Neutral

Posted 22 February 2017 - 07:38

Found this:

 

 

compact_memory

Available only when CONFIG_COMPACTION is set. When 1 is written to the file,
all zones are compacted such that free memory is available in contiguous
blocks where possible. This can be important for example in the allocation of
huge pages although processes will also directly compact memory as required.

 

If add "echo 1 > /proc/sys/vm/compact_memory" in cron will help me?

 

or may be put this

 

vm.overcommit_memory=2

vm.overcommit_ratio=80

 

in sysctl.conf?



Re: Edision osmini(dvb-s2+dvb-t2/c) crashed #22 Erik Slagter

  • PLi® Core member
  • 46,951 posts

+541
Excellent

Posted 23 February 2017 - 17:44

I'd say try it. The worst what can happen is that your receiver crashes even sooner. In the past we used zramfs for this purpose and it appeared to make things even worse.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Edision osmini(dvb-s2+dvb-t2/c) crashed #23 Cofybreak

  • Senior Member
  • 115 posts

0
Neutral

Posted 27 February 2017 - 18:36

Found the problem, i think.

Enigma2 use too much RAM.

 

7fde5199d482e0aa.jpg

 

My plugins:

 

 

root@osmini:/media/hdd# opkg list-installed|grep plugin- | cut -d\  -f1
enigma2-plugin-drivers-dvb-usb-opticombo
enigma2-plugin-extensions-audiosync
enigma2-plugin-extensions-autobackup
enigma2-plugin-extensions-cutlisteditor
enigma2-plugin-extensions-epgrefresh
enigma2-plugin-extensions-foreca
enigma2-plugin-extensions-graphmultiepg
enigma2-plugin-extensions-mediaplayer2
enigma2-plugin-extensions-mediascanner
enigma2-plugin-extensions-moviecut
enigma2-plugin-extensions-openwebif
enigma2-plugin-extensions-pictureplayer
enigma2-plugin-extensions-subssupport
enigma2-plugin-extensions-tmbd
enigma2-plugin-extensions-youtube
enigma2-plugin-skins-pli-hd
enigma2-plugin-softcams-oscam
enigma2-plugin-systemplugins-cablescan
enigma2-plugin-systemplugins-fastscan
enigma2-plugin-systemplugins-hdmicec
enigma2-plugin-systemplugins-hotplug
enigma2-plugin-systemplugins-mphelp
enigma2-plugin-systemplugins-networkbrowser
enigma2-plugin-systemplugins-osd3dsetup
enigma2-plugin-systemplugins-osdpositionsetup
enigma2-plugin-systemplugins-positionersetup
enigma2-plugin-systemplugins-satfinder
enigma2-plugin-systemplugins-skinselector
enigma2-plugin-systemplugins-softwaremanager
enigma2-plugin-systemplugins-videomode
enigma2-plugin-systemplugins-videotune
enigma2-plugin-systemplugins-wirelesslan
gst-plugin-dvbmediasink
gst-plugin-subsink

 

The question is "How to find which plugin eat my RAM?".

My furst choise is epgrefresh, but it scan 1 bouquet and 1 channel.

Every night, of course, but epg.dat is around 8,5MB.

Too little to cause this.

 



Re: Edision osmini(dvb-s2+dvb-t2/c) crashed #24 Erik Slagter

  • PLi® Core member
  • 46,951 posts

+541
Excellent

Posted 27 February 2017 - 18:40

No. User space memory has nothing to do with physical RAM. It would take a course of a week to explain all the nifty details, so I guess you'd have trust me on this one. I've tried to explain it so many times, I don't want to do it yet another time.


Edited by Erik Slagter, 27 February 2017 - 18:40.

* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Edision osmini(dvb-s2+dvb-t2/c) crashed #25 Cofybreak

  • Senior Member
  • 115 posts

0
Neutral

Posted 27 February 2017 - 18:45

OK. Then we wait for new crash :D



Re: Edision osmini(dvb-s2+dvb-t2/c) crashed #26 Erik Slagter

  • PLi® Core member
  • 46,951 posts

+541
Excellent

Posted 27 February 2017 - 18:50

Or use the proper, released drivers, as Athoik already said.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Edision osmini(dvb-s2+dvb-t2/c) crashed #27 Cofybreak

  • Senior Member
  • 115 posts

0
Neutral

Posted 27 February 2017 - 19:19

I`m using last drivers from openpli feed

root@osmini:~# opkg list-installed|grep kernel
kernel-4.10.0 - 4.10-r0.1
kernel-image-4.10.0 - 4.10-r0.1
kernel-module-brcmstb-osmini - 4.10.0+20170220-r0.0
kernel-module-cdfs - 2.6.27-.5.7
kernel-module-ci - 4.10.0+20170220-r0.0
kernel-module-crc-ccitt - 4.10-r0.1
kernel-module-dvb-usb-dvbsky - 4.10-r0.1
kernel-module-dvb-usb-v2 - 4.10-r0.1
kernel-module-ftm4862 - 4.10.0+20170220-r0.0
kernel-module-fts260 - 4.10.0+20170220-r0.0
kernel-module-hci-uart - 4.10-r0.1
kernel-module-ipv6 - 4.10-r0.1
kernel-module-m88ds3103 - 4.10-r0.1
kernel-module-mac80211 - 4.10-r0.1
kernel-module-r8723bs - 4.10.0+4.4.1-r0.3
kernel-module-rt2800lib - 4.10-r0.1
kernel-module-rt2800usb - 4.10-r0.1
kernel-module-rt2x00lib - 4.10-r0.1
kernel-module-rt2x00usb - 4.10-r0.1
kernel-module-si2157 - 4.10-r0.1
kernel-module-si2168 - 4.10-r0.1
kernel-module-sp988x - 4.10.0+20170220-r0.0
kernel-params - 20110114-r0.0


Re: Edision osmini(dvb-s2+dvb-t2/c) crashed #28 Erik Slagter

  • PLi® Core member
  • 46,951 posts

+541
Excellent

Posted 27 February 2017 - 19:20

How long uptime before the problems?


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Edision osmini(dvb-s2+dvb-t2/c) crashed #29 Cofybreak

  • Senior Member
  • 115 posts

0
Neutral

Posted 27 February 2017 - 19:32

I also have some issues that should be fixed:
1) After the exit of hbbtv no OSD
2) Sometimes when changing channel no picture or no sound

 

 

How long uptime before the problems?

 7 to 10 days.

Sometimes less.

With last drivers

20:31:22 up 1 day,  7:58,  load average: 0.00, 0.03, 0.01

For now no issues.



Re: Edision osmini(dvb-s2+dvb-t2/c) crashed #30 Erik Slagter

  • PLi® Core member
  • 46,951 posts

+541
Excellent

Posted 2 March 2017 - 19:40

I'd recommend scheduled reboot once every week. As said, this is really not the only receiver that has this problem, although more expensive receiver tend to have more RAM and then it takes longer before it shows.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Edision osmini(dvb-s2+dvb-t2/c) crashed #31 Cofybreak

  • Senior Member
  • 115 posts

0
Neutral

Posted 4 March 2017 - 19:30

Now trying with set "vm.vfs_cache_pressure = 50" in sysctl.conf

Unfortunately on the third day interrupted power supply in the building.

Now box is up without issues fourth consecutive day, but it is still early to say whether it has any benefit.

So wait...



Re: Edision osmini(dvb-s2+dvb-t2/c) crashed #32 Cofybreak

  • Senior Member
  • 115 posts

0
Neutral

Posted 6 March 2017 - 16:24

Hi again

Today i looking in syslog and found this:

Mar  2 23:24:32 osmini user.alert kernel: CPU 0 Unable to handle kernel paging request at virtual address 00000042, epc == c08b3414, ra == c08b3410
Mar  2 23:24:32 osmini user.warn kernel: Oops[#1]:
Mar  2 23:24:32 osmini user.warn kernel: CPU: 0 PID: 21544 Comm: kworker/0:2 Tainted: P           O    4.10.0 #1
Mar  2 23:24:32 osmini user.warn kernel: Workqueue: events brcmstb_sync_timer_work [brcmstb_osmini]
Mar  2 23:24:32 osmini user.warn kernel: task: 8ceec100 task.stack: 8cde0000
Mar  2 23:24:32 osmini user.warn kernel: $ 0   : 00000000 10008f00 00000000 c0b5eaa0
Mar  2 23:24:32 osmini user.warn kernel: $ 4   : 10008f01 10008f01 00000001 00000200
Mar  2 23:24:32 osmini user.warn kernel: $ 8   : 00000000 00000000 f4240000 ffffffff
Mar  2 23:24:32 osmini user.warn kernel: $12   : 00000000 00000400 00000000 0000ba7e
Mar  2 23:24:32 osmini user.warn kernel: $16   : 8f750600 c08ab5bc 8ce0c780 c08ab628
Mar  2 23:24:32 osmini user.warn kernel: $20   : 00000000 c08b25e8 00000000 8f720000
Mar  2 23:24:32 osmini user.warn kernel: $24   : 00000000 80083050                 
Mar  2 23:24:32 osmini user.warn kernel: $28   : 8cde0000 8cde1e08 c08b0000 c08b3410
Mar  2 23:24:32 osmini user.warn kernel: Hi    : 00000000
Mar  2 23:24:32 osmini user.warn kernel: Lo    : 00000000
Mar  2 23:24:32 osmini user.warn kernel: epc   : c08b3414 BSYNClib_Channel_P_GenerateCallbacks+0x88/0x388 [brcmstb_osmini]
Mar  2 23:24:32 osmini user.warn kernel: ra    : c08b3410 BSYNClib_Channel_P_GenerateCallbacks+0x84/0x388 [brcmstb_osmini]
Mar  2 23:24:32 osmini user.warn kernel: Status: 10008f03 KERNEL EXL IE
Mar  2 23:24:32 osmini user.warn kernel: Cause : 00800008 (ExcCode 02)
Mar  2 23:24:32 osmini user.warn kernel: BadVA : 00000042
Mar  2 23:24:32 osmini user.warn kernel: PrId  : 0002a065 (Broadcom BMIPS4380)
Mar  2 23:24:32 osmini user.warn kernel: Modules linked in: ipv6 r8723bs(O) hci_uart brcmstb_osmini(PO) sp988x(O) ci(O) ftm4862(PO) fts260(PO)
Mar  2 23:24:32 osmini user.warn kernel: Process kworker/0:2 (pid: 21544, threadinfo=8cde0000, task=8ceec100, tls=00000000)
Mar  2 23:24:32 osmini user.warn kernel: Stack : 00000001 00000001 8cde0000 8cde1e38 8ce0b900 c08b37f0 c08ab1b4 d4eb41e3
Mar  2 23:24:32 osmini user.warn kernel:         c08b70a0 c08b7288 00000001 8f750600 81213500 00000000 80a00000 80a00000
Mar  2 23:24:32 osmini user.warn kernel:         8ce0b900 c08b3844 80a00000 8f750600 8f366080 00000000 00000001 c08b38cc
Mar  2 23:24:32 osmini user.warn kernel:         8ce0b900 8ce0b900 8f366080 00000000 81216700 800532ac 00000008 81213518
Mar  2 23:24:32 osmini user.warn kernel:         80a00000 81213700 80a00000 80a00000 81213500 8ce0b918 00000008 81213518
Mar  2 23:24:32 osmini user.warn kernel:         ...
Mar  2 23:24:32 osmini user.warn kernel: Call Trace:
Mar  2 23:24:32 osmini user.warn kernel: [<c08b3414>] BSYNClib_Channel_P_GenerateCallbacks+0x88/0x388 [brcmstb_osmini]
Mar  2 23:24:32 osmini user.warn kernel: [<c08b3844>] BSYNClib_Channel_P_Process+0x130/0x198 [brcmstb_osmini]
Mar  2 23:24:32 osmini user.warn kernel: [<800532ac>] process_one_work+0x168/0x40c
Mar  2 23:24:32 osmini user.warn kernel: [<800536bc>] worker_thread+0x16c/0x60c
Mar  2 23:24:32 osmini user.warn kernel: [<80059d4c>] kthread+0x140/0x170
Mar  2 23:24:32 osmini user.warn kernel: [<80016148>] ret_from_kernel_thread+0x14/0x1c
Mar  2 23:24:32 osmini user.warn kernel: Code: 0260f809  00000000  0040a025 <90420042> 10400004  8e870000  92820070  1440001d  02c03025
Mar  2 23:24:32 osmini user.warn kernel: ---[ end trace 1548cc37647ea2f2 ]---

However, STB is working normally and I have not noticed any problems.

Current uptime:

root@osmini:~# uptime
17:08:02 up 6 days,  4:38,  load average: 0.00, 0.00, 0.00

Memory status:

root@osmini:~# egrep "Mem|Cached|Swap" /proc/meminfo
MemTotal:         248932 kB
MemFree:          132592 kB
MemAvailable:     146544 kB
Cached:            15640 kB
SwapCached:           76 kB
SwapTotal:        262140 kB
SwapFree:         261620 kB

root@osmini:~# cat /proc/buddyinfo
Node 0, zone   Normal    360   2435   1337   1080    624     95     13      1      0      0      0

root@osmini:~# cat /sys/kernel/debug/extfrag/extfrag_index
Node 0, zone   Normal -1.000 -1.000 -1.000 -1.000 -1.000 -1.000 -1.000 -1.000 0.978 0.989 0.995

Firmware version:  OpenPLi 4.0 (2017-02-24)
Kernel / Drivers:  4.10.0 / 4.10.0+20170220-r0.0



Re: Edision osmini(dvb-s2+dvb-t2/c) crashed #33 Erik Slagter

  • PLi® Core member
  • 46,951 posts

+541
Excellent

Posted 6 March 2017 - 19:45

That may very well be the start of the problem.

 

Kernel OOPS means driver bug (most probably) or hardware failure (less probably).


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Edision osmini(dvb-s2+dvb-t2/c) crashed #34 Cofybreak

  • Senior Member
  • 115 posts

0
Neutral

Posted 18 March 2017 - 17:11

Hi, again

Just to inform.

STB reached 19 days uptime, while again not stop power supply in the building.

This is longer uptime for last 4 mounts.

So, problem solved.

Thanks for yours help. Regads.




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users