beta2

[mk01]

(23rd Nov, 2013 09:58 AM)f1vefour Wrote:  @mk01

I'm getting this and while it happens XBMC CPU usage spikes, it is certainly a kernel compatibility issue with lirc_rpi and the Ethernet driver.

http://pastebin.com/GwdzyLU5

*edit*
So far disabling turbo on Ethernet and changing vfs_cache_pressure to 300 has resolved the issue, doesn't really seem to affect LAN speeds either.

@f1vefour

retest with xbian-update 1.0.2-11c. but actually it is only netturbo=N and cache pressure default kept. but shorter interval between dirty write backs - should have similar effect as cache pressure.

@CurlyMo

where is the original xbian_lirc_kernel patch from?

---

(1st Dec, 2013 08:53 PM)Killerbee Wrote:  CPU in htop goes max BUT I am not able to see what process! It's not the dpkg update process. So I assume it's the kernel/zram (I am not an expert here).

htop keeps running but as soon as I stop htop terminal (first ssh shell) is not responding. So I am unable to run dmesg.

So installation failed.

Second test.
Same as above but before updating i manually copied the content of the new xbian.conf from the new xbian-update_1.0.2-11 package to /etc/sysctrl.conf and /etc/default/xbian.conf files.

Reboot and ran the update procedure.

Result was the same. So update failed (stalled)

@Killerbee

actually yes, I have one suggestion - to follow the steps I posted precisely.

what you did is not going to help help. this because
1) the file which needs to be updated is /etc/sysctl.d/xbian.conf
2) parameters from the file are put into effect very very early during boot process - if you only change file, nothing happens.
3) you updated /etc/sysctl.conf with correct values but kept /etc/sysctl.d/xbian.conf as it was before. during reboot then this happens:
- values are read/set from sysctl.conf file.
- values are then read/set (overwritted) with again old values from xbian.conf (located at /etc/sysctl.d).
- we are exactly where we were.

if you have extracted /etc/sysctl.d/xbian.conf you can just copy it over (but to correct location) and reboot.

and to see the process, you simple "top", when started press "i", then "c", "s", "1" and [enter]. but I suppose it is "mmcqd" (kernel thread writing physical data to mmc media card).