
Weird. That's how I usually configure/install new kernels too...dennisn wrote:I just tried "make oldconfig"ing from 2.6.37, to 2.6.38.2, as I've done countless times before, except this time something is seriously wrong -- the second grub loads the new kernel, there is an endless stream of backtrace-type debug messages that flood my screen -- I have no way of reading what's going on. What the heck happened?!?
I did that and it works fine. Bad compile perhaps? I once had a kernel that didn't work, and with no changes to its .config it worked after a recompile. File corruption or something. Or perhaps support for some hardware was dropped, which your computer needed.VinzC wrote:Weird. That's how I usually configure/install new kernels too...dennisn wrote:I just tried "make oldconfig"ing from 2.6.37, to 2.6.38.2, as I've done countless times before, except this time something is seriously wrong -- the second grub loads the new kernel, there is an endless stream of backtrace-type debug messages that flood my screen -- I have no way of reading what's going on. What the heck happened?!?

Known upstream apparently.dennisn wrote:broke my resuming from hibernation

As this is something seldom used, I tried with emerging geany, nano, mlview, kile and hexedit with different MAKEOPTS:DestroyFX wrote:Here from the timed kernel compilation test I made, with my X6 CPU:
(... snip ...)
The optimal compilation speed was with -jCore. The performance go down with -jCore+1 and more.
I remember that with the 2.6.36-, -jCore+1 was better except with BFS who required -jCore (and was more fast than without BFS with -jCore+1).
Code: Select all
# time emerge --oneshot geany nano mlview kile hexedit
>>> Emerging (1 of 5) app-editors/hexedit-1.2.12
>>> Emerging (2 of 5) dev-util/geany-0.20
>>> Emerging (3 of 5) app-editors/nano-2.2.5
>>> Installing (1 of 5) app-editors/hexedit-1.2.12
>>> Emerging (4 of 5) app-editors/mlview-0.9.0
>>> Emerging (5 of 5) app-editors/kile-2.1_beta5
>>> Installing (3 of 5) app-editors/nano-2.2.5
>>> Installing (2 of 5) dev-util/geany-0.20
>>> Installing (5 of 5) app-editors/kile-2.1_beta5
>>> Installing (4 of 5) app-editors/mlview-0.9.0
>>> Jobs: 5 of 5 complete Load avg: 5.73, 4.35, 3.05
real 3m59.929s
user 8m1.822s
sys 1m5.482sCode: Select all
real 2m10.122s
user 2m23.061s
sys 0m36.148sCode: Select all
real 1m37.223s
user 2m25.297s
sys 0m34.484sCode: Select all
real 1m36.465s
user 2m24.854s
sys 0m34.618sCode: Select all
# make clean && time make -j 4
real 4m18.876s
user 13m24.801s
sys 1m9.835sCode: Select all
# make clean && time make -j 7
real 4m35.801s
user 14m7.941s
sys 1m11.109sCode: Select all
# make clean && time make -j 11
real 4m16.216s
user 14m7.978s
sys 1m9.202sCode: Select all
# make clean && time make -j 15
real 4m23.011s
user 14m11.338s
sys 1m9.929sIsn't to me. "Performs" is not the appropriate term. The patch doesn't improve compile times, it just improves responsiveness, which is totally different. It means, for instance, at equal load, groups of interactive processes in the same session will have better chances to catch a keyboard/mouse events on time and actually *do* the requested operation in a timely fashion. But globally I expect compile times to be just slightly bigger than before.Yamakuzure wrote:This certainly is weird. While using -j7 performs worse than -j4 (like suggested by your tests), -j15 performs better than -j7 and -j11 performs better than -j4. It's not much, but it is strange... (Or not so strange at all if I understood more of the internal mechanics)


Code: Select all
#make clean && time make -j4
real 2m53.167s
user 8m58.095s
sys 0m43.128s
ricker linux # ls -alh arch/x86/boot/bzImage
-rw-r--r-- 1 root root 5.9M Apr 7 03:17 arch/x86/boot/bzImage #roughly half of this is embedded initramfs

The only thing you've proven is that in running a few tests that things worked well on your systemYamakuzure wrote:Well, yes, during all these time tests my laptop was perfectly responsive all the time. I just did the tests because someone stated that it would be stupid to use a different value for the -j option than the number of logical CPUs. That has been proven wrong, now.


The only way to know for sure on your system is to switch to the task grouping and rebuild the kernel.VanFanel wrote:I've been using BFS since 2.6.32: thanks for the ck-sources package, it's what makes my system so great!
But.. would you recommend automatic task grouping over BFS for emulation?
I'm trying to build a near-zero latency system for both audio & input in emulators and I don't know if BFS is the best option for it.
regards
Code: Select all
schedtool -I -e ./mame tekken2Annoying, but since .38 patches a problem I was having with btrfs I can't really switch back. Any idea whether the patch will be reversed?PaulBredbury wrote:Known upstream apparently.dennisn wrote:broke my resuming from hibernation
This seems to happen with 2.6.37-r4 as well thoughPaulBredbury wrote:Known upstream apparently.dennisn wrote:broke my resuming from hibernation
Just apply the patch yourself in the meantime.jbouzan wrote:Annoying, but since .38 patches a problem I was having with btrfs I can't really switch back. Any idea whether the patch will be reversed?PaulBredbury wrote:Known upstream apparently.dennisn wrote:broke my resuming from hibernation
404 Not foundmarshmallow1304 wrote:
Just apply the patch yourself in the meantime.
https://patchwork.kernel.org/patch/690691/