Reply
Thread Tools
Posts: 1,163 | Thanked: 1,873 times | Joined on Feb 2011 @ The Netherlands
#151
I used maacruz kernel(pwck2) and experienced massive UI/graphical lags and even lock-ups, nothing is responding to input and needed to put my N900 away, till cpu/IO load was lessened . Then went back to omap1 (stock) and didn't experience anylags or lock-ups.

BTW
I used max freq = 900 mhz with SR on maacruz kernel. So maybe one of the patches was bugging. Trying pw49 now..
 

The Following User Says Thank You to mr_pingu For This Useful Post:
Posts: 1,101 | Thanked: 1,184 times | Joined on Aug 2008 @ Spain
#152
Originally Posted by mr_pingu View Post
I used maacruz kernel(pwck2) and experienced massive UI/graphical lags and even lock-ups, nothing is responding to input and needed to put my N900 away, till cpu/IO load was lessened . Then went back to omap1 (stock) and didn't experience anylags or lock-ups.

BTW
I used max freq = 900 mhz with SR on maacruz kernel. So maybe one of the patches was bugging. Trying pw49 now..
Could you try this new build and check if the lags are gone?
https://garage.maemo.org/frs/downloa...wck3_armel.deb
https://garage.maemo.org/frs/downloa...wck3_armel.deb
https://garage.maemo.org/frs/downloa...wck3_armel.deb
 
Posts: 3,074 | Thanked: 12,960 times | Joined on Mar 2010 @ Sofia,Bulgaria
#153
Originally Posted by maacruz View Post
...About those patches, 0001 and 0002 change spinlocks to mutexes, so may be they cause trouble (look at 0002 comments).
Good luck!
With those 2 disabled there are no crashes so far. Will run that kernel for several days more to be 100% sure.

What did you change in the .debs attached to your last post?
 

The Following User Says Thank You to freemangordon For This Useful Post:
Posts: 1,163 | Thanked: 1,873 times | Joined on Feb 2011 @ The Netherlands
#154
From now on I am testing these Will report back...
 

The Following User Says Thank You to mr_pingu For This Useful Post:
Posts: 3,074 | Thanked: 12,960 times | Joined on Mar 2010 @ Sofia,Bulgaria
#155
Originally Posted by mr_pingu View Post
From now on I am testing these Will report back...
@Pali - can you put some script in kernel-power-settings(kernel-config) to automatically replace 700,750 frequencies with 720 on profile load, using the voltage for 750? With some sort of a warning "you are using a deprecated frequencies, bla, bla". As I am afraid there will be an avalanche of reports "my battery, my CPU,..." once those go into extras.

Your scripting skills are better than mine, that's why it is better you to do it .
 

The Following 5 Users Say Thank You to freemangordon For This Useful Post:
Posts: 1,101 | Thanked: 1,184 times | Joined on Aug 2008 @ Spain
#156
Originally Posted by freemangordon View Post
With those 2 disabled there are no crashes so far. Will run that kernel for several days more to be 100% sure.

What did you change in the .debs attached to your last post?
Disabled the 0001-mtd and 0002-mtd patches as I think they were causing the slowdown during memory swapping.
For some reason they caused reboots in your device, while in mine only some slowdowns I failed to properly notice by putting the blame elsewere until mr-pingu opened my eyes.
Disabled thumb2 and mesh wireless too, as they have been reported here to cause instability.
It is also a 512hz kernel, as I have been running with that frequency since we first talked about it.
 
Posts: 3,074 | Thanked: 12,960 times | Joined on Mar 2010 @ Sofia,Bulgaria
#157
Originally Posted by maacruz View Post
Disabled the 0001-mtd and 0002-mtd patches as I think they were causing the slowdown during memory swapping.
For some reason they caused reboots in your device, while in mine only some slowdowns I failed to properly notice by putting the blame elsewere until mr-pingu opened my eyes.
Disabled thumb2 and mesh wireless too, as they have been reported here to cause instability.
It is also a 512hz kernel, as I have been running with that frequency since we first talked about it.
On the other hand those patches really seem like something useful, if there wasn't the problem they've introduced.

Is there a chance to build and test the kernel with those patches enabled and:

CONFIG_DEBUG_KERNEL=y
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_DEBUG_MUTEXES=y

and/or similar (can't remember the exact flags for spinlock/mutex debugging) to see what is going on. I have bridgedriver debugging session to do here

BTW I have compcache swap, that might be the reason for reboots on my device.
 

The Following 2 Users Say Thank You to freemangordon For This Useful Post:
Posts: 1,163 | Thanked: 1,873 times | Joined on Feb 2011 @ The Netherlands
#158
Noticed not a single lag with this new kernel, maacruz. Thinking of adding 720p support, as I think it's smoother than kp49 or is that just me?

Need more info, logs of testing from me?

Am I the only one who always wondered why the omap1 kernel was running so smooth with only 600 mhz?
 

The Following 3 Users Say Thank You to mr_pingu For This Useful Post:
Posts: 1,101 | Thanked: 1,184 times | Joined on Aug 2008 @ Spain
#159
Originally Posted by freemangordon View Post
On the other hand those patches really seem like something useful, if there wasn't the problem they've introduced.

Is there a chance to build and test the kernel with those patches enabled and:

CONFIG_DEBUG_KERNEL=y
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_DEBUG_MUTEXES=y

and/or similar (can't remember the exact flags for spinlock/mutex debugging) to see what is going on. I have bridgedriver debugging session to do here

BTW I have compcache swap, that might be the reason for reboots on my device.
I can try, but right now I'm looking at the patches and wondering what causes the problem:
0002-mtd should have no noticeable effect in the N900. If you look at the end of the patch...
Code:
/* This is used to handle contention on write/erase operations
    between partitions of the same physical chip. */
The N900 only uses one mtd partition, rootfs, so there can't be contention for accessing different partitions.

Now about 0001-mtd. It is a pretty straight forward patch, just replace all spinlocks with mutexes.
This patch shouldn't affect memory swapping because it takes place in mmc, not mtd, so the slowdown has to happen when a mmapped large file has been unmapped and then it is remapped again, a common scenario for executable files. Why the slowdown? The only reason I can think of is because the mutex has already been adquired.
If we look at the description text:
I have checked the code of the drivers and there is no use of atomic
pathes like interrupt or timers. The mtdoops facility will also not be used
by this drivers. So it is dave to replace the spin_lock against mutex.

There is no performance regression since the mutex is normally not
acquired.
Looking at the Nokia patches (2.6.28-omap1.diff) I see a lot of changes to the mtd subsystem, including a new mtd driver, so it is quite possible that the assumptions taken for this patch are wrong in the N900, requiring substantial rework.
Since it is doubtful that this patch could provide any noticeable gain in the N900, and it is confirmed that it causes problems, and it would require a lot of work, I think it is better just to drop them.

Last edited by maacruz; 2012-02-09 at 23:13.
 

The Following 2 Users Say Thank You to maacruz For This Useful Post:
Posts: 1,101 | Thanked: 1,184 times | Joined on Aug 2008 @ Spain
#160
Originally Posted by mr_pingu View Post
Noticed not a single lag with this new kernel, maacruz. Thinking of adding 720p support, as I think it's smoother than kp49 or is that just me?
720p is already enabled in the kernel, although I haven't tested it yet, so you can go ahead and install the debs if you wish.
The ck patches are supposed to increase performance for desktop-like usage patterns, so it is possible that it were "smoother".
Need more info, logs of testing from me?

Am I the only one who always wondered why the omap1 kernel was running so smooth with only 600 mhz?
No, but now that you already mentioned it, if you like testing it would be interesting to test if there is any difference at all in HD recording performance or jerkiness compared to kp49.
 
Reply

Tags
development, kernel-power


 
Forum Jump


All times are GMT. The time now is 07:53.