![]() |
Re: BFS for the power kernel
hmm... after installing the latest kernel with bfq I got into an reboot loop. guess i have to reflash it.
|
Re: BFS for the power kernel
Quote:
|
Re: BFS for the power kernel
Well I reflashed the kernel (I think I just forgot to install the flasher this time hence the reboot loop) so it's working fine now. BFQ is also enabled, so far no crashes but I guess I'll have to test more.
|
Re: BFS for the power kernel
Quote:
Code:
strings /dev/mtd2ro > /home/user/MyDocs/log.txt |
Re: BFS for the power kernel
1 Attachment(s)
Quote:
|
Re: BFS for the power kernel
Hmm, there are a whole lot of the null reference errors there, all caused by BFQ. Not good. Could you check that /syspart is being mounted correctly, and that bfq.ioprio, bfq.ioprio_class and bfq.weight are all present under that directory (when BFQ is the default scheduler, of course)? You could set it just for mmcblk1, if you've an external SD.. I am guessing that /usr/lib/libohm_cgroups.so is present and loaded?
|
Re: BFS for the power kernel
Quote:
Code:
cgroup /syspart cgroup rw,bfqio,freezer,memory 0 0 Code:
/syspart/bfqio.ioprio: 0 |
Re: BFS for the power kernel
Yep, it seems to definitely be loaded. Did you have bfq as the default scheduler for mmcblk0, if so then setting it on mmcblk1 wouldn't change anything in /syspart.. it's also possible that bfqio is enabled regardless of whether bfq is or not, and just sits idle until called upon. Ok, could you please try one of these (depending on your setup - the modules should be unchanged), I have disabled the "queue small requests" part of BFQ v2 r1 and have been running it happily on my device for a full day without any crashes..
Multiboot deb Standard deb (use with flasher) U-Boot image |
Re: BFS for the power kernel
Quote:
Hmm I'm still getting crashes immediately after activating bfq. |
Re: BFS for the power kernel
Do you have any applications etc running when you change to the BFQ scheduler? I activate it in an /etc/event.d script, but it would probably be fine to do so after reboot from X-term - not so sure if you've had the system running for several hours/days beforehand, though.
|
All times are GMT. The time now is 18:40. |
vBulletin® Version 3.8.8