

Code: Select all
====================================
Timed PHP Compilation 5.2.9
Time To Compile
====================================
Linux-2.6.31-zen0+CFS: 25.73
Linux-2.6.31-zen0+BFS: 25.65
====================================
Timed Apache Compilation 2.2.11
Time To Compile
====================================
Linux-2.6.31-zen0+CFS: 3.48
Linux-2.6.31-zen0+BFS: 3.41
====================================
7-Zip Compression 4.65
Compress Speed Test
====================================
Linux-2.6.31-zen0+CFS: 18404.00
Linux-2.6.31-zen0+BFS: 17836.66
====================================
Apache Benchmark 2.2.11
Static Web Page Serving
====================================
Linux-2.6.31-zen0+CFS: 8656.34
Linux-2.6.31-zen0+BFS: 13692.08
=====================================================================
Threaded I/O Tester 0.3.3
Test Item: Random Write - Filesize Per Thread: 16MB - Thread Count: 8
=====================================================================
Linux-2.6.31-zen0+CFS: 3.00
Linux-2.6.31-zen0+BFS: 4.00
=============================================================
Threaded I/O Tester 0.3.3
Test Item: Read - Filesize Per Thread: 16MB - Thread Count: 8
=============================================================
Linux-2.6.31-zen0+CFS: 2.00
Linux-2.6.31-zen0+BFS: 2.00
====================================
PostMark 1.51
Disk Transaction Performance
====================================
Linux-2.6.31-zen0+CFS: 1063.50
Linux-2.6.31-zen0+BFS: 967.25

Please post the .config you have for this. I'd be interested to see it.heavyjoost wrote:No problems here and I'm running on an dual-core AMD CPU. Running on Debian (testing) though.pappy_mcfae wrote:No kidding. This machine loves BFS. My future web server loves bfs. My multi-processor machines don't...whether x86 or x86_64. I keep waiting in hope that one of the heads-up emails will find me staring at a patch that will make BFS work on my multiprocessor machines.
Blessed be!
Pappy


Code: Select all
Sep 19 01:05:54 [kernel] [ 170.968470] ------------[ cut here ]------------
Sep 19 01:05:54 [kernel] [ 170.968479] WARNING: at net/mac80211/tx.c:1325 ieee80211_tx+0x23f/0x2d9()
Sep 19 01:05:54 [kernel] [ 170.968485] Hardware name:
Sep 19 01:05:54 [kernel] [ 170.968493] Modules linked in: ipt_REJECT xt_tcpudp iptable_filter ip_tables ip6table_filter ip6_tables x_tables sr_mod p54usb p54common cdrom [last unloaded: microcode]
Sep 19 01:05:54 [kernel] [ 170.968522] Pid: 0, comm: swapper Tainted: G W 2.6.31-zen0 #17
Sep 19 01:05:54 [kernel] [ 170.968527] Call Trace:
Sep 19 01:05:54 [kernel] [ 170.968531] <IRQ> [<ffffffff8103486e>] warn_slowpath_common+0x88/0xb6
Sep 19 01:05:54 [kernel] [ 170.968547] [<ffffffff8103491f>] warn_slowpath_fmt+0x4b/0x61
Sep 19 01:05:54 [kernel] [ 170.968558] [<ffffffff813292ee>] ieee80211_tx+0x23f/0x2d9
Sep 19 01:05:54 [kernel] [ 170.968570] [<ffffffff8132954f>] ieee80211_tx_pending+0x1c7/0x2de
Sep 19 01:05:54 [kernel] [ 170.968580] [<ffffffff8133ade2>] ? _spin_unlock+0x3d/0x5c
Sep 19 01:05:54 [kernel] [ 170.968590] [<ffffffff810397d2>] tasklet_action+0x7e/0xe0
Sep 19 01:05:54 [kernel] [ 170.968600] [<ffffffff8103a0e6>] __do_softirq+0xa5/0x151
Sep 19 01:05:54 [kernel] [ 170.968609] [<ffffffff8101f5aa>] ? apic_write+0x24/0x3a
Sep 19 01:05:54 [kernel] [ 170.968618] [<ffffffff8100ce2c>] call_softirq+0x1c/0x28
Sep 19 01:05:54 [kernel] [ 170.968628] [<ffffffff8100ee9f>] do_softirq+0x43/0x98
Sep 19 01:05:54 [kernel] [ 170.968637] [<ffffffff8103a35b>] irq_exit+0x52/0xb6
Sep 19 01:05:54 [kernel] [ 170.968646] [<ffffffff8100e55a>] do_IRQ+0xb3/0xe0
Sep 19 01:05:54 [kernel] [ 170.968655] [<ffffffff8100c693>] ret_from_intr+0x0/0xa
Sep 19 01:05:54 [kernel] [ 170.968661] <EOI> [<ffffffff81013b45>] ? mwait_idle+0x76/0x8f
Sep 19 01:05:54 [kernel] [ 170.968676] [<ffffffff81013b38>] ? mwait_idle+0x69/0x8f
Sep 19 01:05:54 [kernel] [ 170.968685] [<ffffffff8100b06a>] ? cpu_idle+0xaa/0x10e
Sep 19 01:05:54 [kernel] [ 170.968694] [<ffffffff8132e64e>] ? rest_init+0x92/0xa8
Sep 19 01:05:54 [kernel] [ 170.968704] [<ffffffff814c5a2b>] ? start_kernel+0x317/0x338
Sep 19 01:05:54 [kernel] [ 170.968714] [<ffffffff814c4e61>] ? x86_64_start_reservations+0x91/0xac
Sep 19 01:05:54 [kernel] [ 170.968725] [<ffffffff814c4f6d>] ? x86_64_start_kernel+0xf1/0x10c
Sep 19 01:05:54 [kernel] [ 170.968732] ---[ end trace 0b83a2ce3dfaf3d9 ]---
Zen has the latest cfs (almost, there are new updates to add now)HecHacker1 wrote:Regarding the Phoronix BFS vs mainline benchmarks, lots of discussion is happening on the linux kernel mailing lists.
The gist of it is that CFS can perform better than BFS, but only with changes to the many scheduler sys controls in /proc/sys/kernel/.
If you want to go through the whole thread:
http://lkml.org/lkml/2009/9/6/136
You'll see lots of discussion, with many patches to CFS after discovering BFS did much better at some tasks.
That's good news, and we probably would have never seen these patches without BFS as competition.
Overall it seems BFS isn't particularly bad at anything, and yet is a much simpler scheduler with fewer tuneables.
Maybe we can get the Zen dev's to pull the latest CFS changes? And perhaps use some of the suggested tuneables in the threads.
I'll be sticking with BFS though just to test it out. Con is still improving it, he's on BFS v222-test4 right now, which seems to further simplify and fix fairness issues.

You need to go to #zen-sources on irc.freenode.org and talk to dodo1122 or anyone else and you can get sorted out quickerAnt_P wrote:My wifi crashes are back again. Using this box as a hostapd access point, and it dies if I try to connect to it.
Switching schedulers made no difference here.Code: Select all
Sep 19 01:05:54 [kernel] [ 170.968470] ------------[ cut here ]------------ Sep 19 01:05:54 [kernel] [ 170.968479] WARNING: at net/mac80211/tx.c:1325 ieee80211_tx+0x23f/0x2d9() Sep 19 01:05:54 [kernel] [ 170.968485] Hardware name: Sep 19 01:05:54 [kernel] [ 170.968493] Modules linked in: ipt_REJECT xt_tcpudp iptable_filter ip_tables ip6table_filter ip6_tables x_tables sr_mod p54usb p54common cdrom [last unloaded: microcode] Sep 19 01:05:54 [kernel] [ 170.968522] Pid: 0, comm: swapper Tainted: G W 2.6.31-zen0 #17 Sep 19 01:05:54 [kernel] [ 170.968527] Call Trace: Sep 19 01:05:54 [kernel] [ 170.968531] <IRQ> [<ffffffff8103486e>] warn_slowpath_common+0x88/0xb6 Sep 19 01:05:54 [kernel] [ 170.968547] [<ffffffff8103491f>] warn_slowpath_fmt+0x4b/0x61 Sep 19 01:05:54 [kernel] [ 170.968558] [<ffffffff813292ee>] ieee80211_tx+0x23f/0x2d9 Sep 19 01:05:54 [kernel] [ 170.968570] [<ffffffff8132954f>] ieee80211_tx_pending+0x1c7/0x2de Sep 19 01:05:54 [kernel] [ 170.968580] [<ffffffff8133ade2>] ? _spin_unlock+0x3d/0x5c Sep 19 01:05:54 [kernel] [ 170.968590] [<ffffffff810397d2>] tasklet_action+0x7e/0xe0 Sep 19 01:05:54 [kernel] [ 170.968600] [<ffffffff8103a0e6>] __do_softirq+0xa5/0x151 Sep 19 01:05:54 [kernel] [ 170.968609] [<ffffffff8101f5aa>] ? apic_write+0x24/0x3a Sep 19 01:05:54 [kernel] [ 170.968618] [<ffffffff8100ce2c>] call_softirq+0x1c/0x28 Sep 19 01:05:54 [kernel] [ 170.968628] [<ffffffff8100ee9f>] do_softirq+0x43/0x98 Sep 19 01:05:54 [kernel] [ 170.968637] [<ffffffff8103a35b>] irq_exit+0x52/0xb6 Sep 19 01:05:54 [kernel] [ 170.968646] [<ffffffff8100e55a>] do_IRQ+0xb3/0xe0 Sep 19 01:05:54 [kernel] [ 170.968655] [<ffffffff8100c693>] ret_from_intr+0x0/0xa Sep 19 01:05:54 [kernel] [ 170.968661] <EOI> [<ffffffff81013b45>] ? mwait_idle+0x76/0x8f Sep 19 01:05:54 [kernel] [ 170.968676] [<ffffffff81013b38>] ? mwait_idle+0x69/0x8f Sep 19 01:05:54 [kernel] [ 170.968685] [<ffffffff8100b06a>] ? cpu_idle+0xaa/0x10e Sep 19 01:05:54 [kernel] [ 170.968694] [<ffffffff8132e64e>] ? rest_init+0x92/0xa8 Sep 19 01:05:54 [kernel] [ 170.968704] [<ffffffff814c5a2b>] ? start_kernel+0x317/0x338 Sep 19 01:05:54 [kernel] [ 170.968714] [<ffffffff814c4e61>] ? x86_64_start_reservations+0x91/0xac Sep 19 01:05:54 [kernel] [ 170.968725] [<ffffffff814c4f6d>] ? x86_64_start_kernel+0xf1/0x10c Sep 19 01:05:54 [kernel] [ 170.968732] ---[ end trace 0b83a2ce3dfaf3d9 ]---
I noticed the line "using mwait in idle threads." in my boot messages, does that mean there's possibly a way to turn it off and avoid this crash?
edit: Answered my own question - yes there is (idle=halt) and yes it fixes it.
edit 2: I was wrong... that only delayed it. I've recompiled and turned off "enable wireless powersave by default" in the networking options to see if that was it.
edit 3: Nope. I give up, going back to .31 vanilla for now though I'm not getting my hopes up for that either...


ReiserFS 3.6 is broken with BFS.Jupiter1TX wrote:Not sure why but two times now while using 2.6.31-zen1+BFS
my /usr/portage index gets corrupted when trying to update
using eix-sync and, i have had to recreate my portage partition.
This has never happened without BFS. Am using reiserfs3 and
Funtoo.
No need, it seems to be stable again after going back to 2.6.31-zen1 (instead of git HEAD). I don't think I should be bugging people directly about it at the moment, at least until the .32-rc's start coming.cheater1034 wrote:You need to go to #zen-sources on irc.freenode.org and talk to dodo1122 or anyone else and you can get sorted out quicker

/facepalmAnt_P wrote:No need, it seems to be stable again after going back to 2.6.31-zen1 (instead of git HEAD). I don't think I should be bugging people directly about it at the moment, at least until the .32-rc's start coming.cheater1034 wrote:You need to go to #zen-sources on irc.freenode.org and talk to dodo1122 or anyone else and you can get sorted out quicker

Please if the bug occurs on master-2.6.31 (which is now labeled as zen2) go into IRC and help find it if it's zen-related !Ant_P wrote:I guess I deserved those crashes for not paying attention.
With 2.6.31-zen1, those warnings are still there and they apparently cause the wifi to stop working. It looks like the crash was something else entirely (maybe triggered by this though), because it's been running for hours with no other problems.
Code: Select all
# genkernel --disklabel all
* Gentoo Linux Genkernel; Version 3.4.10.906
* Running with options: --disklabel all
* Linux Kernel 2.6.31-zen0 for x86_64...


Any hope, that it would be fixed?aTan wrote:ReiserFS 3.6 is broken with BFS.Jupiter1TX wrote:Not sure why but two times now while using 2.6.31-zen1+BFS
my /usr/portage index gets corrupted when trying to update
using eix-sync and, i have had to recreate my portage partition.
This has never happened without BFS. Am using reiserfs3 and
Funtoo.

Smeg knows. It forced me to use Reiser4. There is only one thing in BFS FAQ about it:razum2um wrote:Any hope, that it would be fixed?aTan wrote:ReiserFS 3.6 is broken with BFS.Jupiter1TX wrote:Not sure why but two times now while using 2.6.31-zen1+BFS
my /usr/portage index gets corrupted when trying to update
using eix-sync and, i have had to recreate my portage partition.
This has never happened without BFS. Am using reiserfs3 and
Funtoo.
(I have ReiserFS 3 on /home)
I suggest NOT using this with reiserFS3.6
as it uses a very fragile lockless algorithm, although I have no proof that it
will break.
Hopefully I've got enough free time today, just checked out the right branch this time (not the tagged .31-zen1cheater1034 wrote:Please if the bug occurs on master-2.6.31 (which is now labeled as zen2) go into IRC and help find it if it's zen-related !
(trust me, i'm much more concerned with bugs in the stable branches than the dev branches come out) -------- especially 2.6.32-rc, it looks like a handfull

issue these commands inside git treepappy_mcfae wrote:How did you come up with "# Linux kernel version: 2.6.31-zen2 "Alien Mind Creator"", as in the first .config you posted?
Code: Select all
git fetchCode: Select all
git diff v2.6.31 origin/master-2.6.31 > ../2.6.31-zen.patch
http://zen-sources.org/content/master-c ... -using-gitRion wrote:its on master nowwhy zen0 ?Code: Select all
# genkernel --disklabel all * Gentoo Linux Genkernel; Version 3.4.10.906 * Running with options: --disklabel all * Linux Kernel 2.6.31-zen0 for x86_64...
PS i think i'll move got gentoo-sources if my microphone won't work with zen2.. something is really wrong with alsa in zen