BFS for the power kernel - Page 15 - maemo.org

Active Topics

Maemo repository (8)
to Community by Maemish - 1 day, 5 hrs ago
Porting apps to Leste (44)
to Maemo 7 / Leste by norayr - 1 day, 10 hrs ago
List of well performing apps on Leste (35)
to Maemo 7 / Leste by smatkovi - 4 days, 7 hrs ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (13)
to SailfishOS by edp17 - 5 days, 5 hrs ago
Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx) (79)
to SailfishOS by edp17 - 5 days, 5 hrs ago
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 5 days, 10 hrs ago
more...

Page 15 of 31

Thread Tools

	humble	2011-03-31 , 21:24
	Posts: 355 \| Thanked: 396 times \| Joined on Dec 2009 @ USA	#141

Originally Posted by hawaii

Hard locks occurs very randomly and I've yet to experience it in such a manner when using CFS, but I am able to lock up the device on CFS, in any fashion.

With BFS, sometimes it'll lock up when it's under medium load, other times under no load whatsoever. I'll open the status menu, it'll completely halt. Playing a game, reject an incoming call and it'll be hosed. Both the power key and the light sensor (controlling keyboard LED) are unresponsive and I have to battery pull.

i can confirm this, and replicate it. if you set too many high priority's.... i tried with SCHED_RR, but its not normal.

this kernel is about stable as power (good).

and i see the gains especially with scheduling pulseaudio, Xorg

__________________
Would you like to Donate?

My"Current Project(s)":
[Resurrecting] DON

Quote & Reply |

	hawaii	2011-04-14 , 02:29
	Posts: 1,030 \| Thanked: 792 times \| Joined on Jun 2009	#142

FWIW, I'm gone ahead and disabled the watchdogs and have been happy ever since.

Quote & Reply |

	hawaii	2011-05-06 , 16:26
	Posts: 1,030 \| Thanked: 792 times \| Joined on Jun 2009	#143

I've noticed this is the only kernel that has been giving me issues with voice calls.

There's a static white noise overlay over calls that comes in randomly. I've done a lot of testing versus other kernels and it's always present with BFS only. Anybody else notice this or have any insight? I can only assume it's an issue with slicing pulseaudio or another process is getting interrupted?

Quote & Reply |

The Following 3 Users Say Thank You to hawaii For This Useful Post:
Estel, iDont, Mentalist Traceur

Reffyyyy	2011-05-06 , 16:40
Posts: 662 \| Thanked: 653 times \| Joined on Feb 2010	#144

Originally Posted by hawaii

I've noticed this is the only kernel that has been giving me issues with voice calls.

There's a static white noise overlay over calls that comes in randomly. I've done a lot of testing versus other kernels and it's always present with BFS only. Anybody else notice this or have any insight? I can only assume it's an issue with slicing pulseaudio or another process is getting interrupted?

I can confirm this. It isn't consistent and usually disappears after I hang up and call again.

Quote & Reply |

The Following 2 Users Say Thank You to Reffyyyy For This Useful Post:
iDont, Mentalist Traceur

iDont	2011-05-10 , 21:09
Posts: 268 \| Thanked: 1,053 times \| Joined on May 2010 @ The Netherlands	#145

Originally Posted by hawaii

I've noticed this is the only kernel that has been giving me issues with voice calls.

There's a static white noise overlay over calls that comes in randomly. I've done a lot of testing versus other kernels and it's always present with BFS only. Anybody else notice this or have any insight? I can only assume it's an issue with slicing pulseaudio or another process is getting interrupted?

We know about this problem (see this post). We had lots of fun compiling kernels last weeks

. It seems that bfs-350-to-357.patch is responsible. Here's a summary I've sent to Tigerite in a PM:

BFS 330 - sched_reset_on_fork.diff: no distorted calls in two weeks or so
BFS 350 + sched_reset_on_fork.diff: distortion in calls
BFS 350 - sched_reset_on_fork.diff: distortion in calls
BFS 401 - sched_reset_on_fork.diff: distortion in calls

(We already determined the voltage patches in the tree weren't responsible, so the problem was either in a BFS patch or the sched_reset_on_fork patch)

We isolated the changes between our bfs-350-to-357.patch and Con's original bfs330-bfs350.patch. These changes weren't responsible, so we're still not done.

Unfortunately, other projects have been keeping me busy lately and still are. I'm very eager to find the exact piece of code responsible though and will pick the debugging up later.

On other news: the kernel-bfs tree has got BFS v0.401 in it for a while now. Kernel-power v47 will be integrated soon too. These two things combined (or even separately) make a great new kernel-bfs release, but we want to get the distortion sorted out first (or at least have tried the more easier possible fixes).

Last edited by iDont; 2011-05-10 at 21:11.

Quote & Reply |

The Following 6 Users Say Thank You to iDont For This Useful Post:
cheve, drangina, Estel, fw190, hawaii, Mentalist Traceur

	hawaii	2011-05-10 , 23:22
	Posts: 1,030 \| Thanked: 792 times \| Joined on Jun 2009	#146

Any chance of reverting the bluetooth patch that was introduced in power46? It seems to cause issues with hand-off with my A2DP headphones when a call comes in. It drops the transfer but holds the connection still.

Really appreciate the work going into this.

Last edited by hawaii; 2011-05-10 at 23:24.

Quote & Reply |

iDont	2011-05-13 , 15:54
Posts: 268 \| Thanked: 1,053 times \| Joined on May 2010 @ The Netherlands	#147

Originally Posted by hawaii

Any chance of reverting the bluetooth patch that was introduced in power46? It seems to cause issues with hand-off with my A2DP headphones when a call comes in. It drops the transfer but holds the connection still.

Really appreciate the work going into this.

I've noticed some other negative comments about that patch in the kernel-power v47 thread as well. As a result, I've disabled the patch in our tree for now.

Kernel-bfs has also been updated to reflect the changes kernel-power v47 brought. Furthermore, Reiser4* support has been included. No updates on the distortion though.

*Reiser4progs & libaal are in Maemo's extras-devel

Quote & Reply |

The Following 5 Users Say Thank You to iDont For This Useful Post:
cheve, fw190, hawaii, Mentalist Traceur, Tigerite

Radicalz38	2011-05-14 , 00:33
Posts: 1,042 \| Thanked: 430 times \| Joined on May 2010	#148

Hi! Just asking is it possible to reupdate the bfs kernel with wl1251 driver support? The previous version is already too outdated and would really want the new patches specially Reiser4 support. And the disabled bluetooth patch as it causes problems with me also :/

Quote & Reply |

	Estel	2011-05-14 , 05:15
	Posts: 5,028 \| Thanked: 8,613 times \| Joined on Mar 2011	#149

As it was mentioned here:
http://talk.maemo.org/showpost.php?p...&postcount=556

The bluetooth patch introduced in kp46 (and remain the same in kp47) is probably not the cause of problems, so removing it with such a haste may be fail move, only breaking compatibility with many bluetooth mouses.

Quote & Reply |

The Following 3 Users Say Thank You to Estel For This Useful Post:
fw190, iDont, Mentalist Traceur

iDont	2011-05-15 , 10:57
Posts: 268 \| Thanked: 1,053 times \| Joined on May 2010 @ The Netherlands	#150

Originally Posted by Radicalz38

Hi! Just asking is it possible to reupdate the bfs kernel with wl1251 driver support? The previous version is already too outdated and would really want the new patches specially Reiser4 support. And the disabled bluetooth patch as it causes problems with me also :/

Kernel-bfs already contains the wl1251 driver, just like the default kernel and kernel-power. If you mean updating it to the bleeding edge wifi drivers from lxp: I'm afraid I don't have the time to do that.
I'm also not sure whether they should be integrated at all, considering how nicely they can be distributed as stand alone packages (but that's just my opinion).

Originally Posted by Estel

As it was mentioned here:
http://talk.maemo.org/showpost.php?p...&postcount=556

The bluetooth patch introduced in kp46 (and remain the same in kp47) is probably not the cause of problems, so removing it with such a haste may be fail move, only breaking compatibility with many bluetooth mouses.

Thanks for the pointer. I don't have any bluetooth hardware to verify any problems, so I have to rely on reports from other people. Even though the bluetooth patch may not be related to those problems at all, I am still seeing posts stating they do experience problems with it (whether those are false or not). I'll re-enable the patch if it either is proven OK or updated.