| View previous topic :: View next topic |
| Author |
Message |
fallow
Bodhisattva
Joined: 08 Jan 2004
Posts: 2208
Location: Poland
|
 Posted: Fri May 27, 2005 12:00 am Post subject: [testing_period] 2.6.12-rc5-love1 (UPDATE03) |
 |
|
[ 27.05.2005] *** UPDATE 01 - > RTP from 09 to 10 ( THX Gringo for the fast info )
[ 27.05.2005] *** UPDATE 02 - > inotify-44-update-2.patch kicked out ( oops ) now is ok
[ 27.05.2005] *** UPDATE 03 - > RTP from 10 to 12
actual size & md5 | Code: | | MD5 29cc3fd371ef717ade79c4e86a2de5e4 2.6.12-rc5-love1.bz2 567846 |
this is testing version , not official release.
If everythings will be ok , it will be marked as official release.
If not , then will be cancelled .
*** In Love-Sources features menu :
*** Default Options are SAFE and GOOD working on x86
*** RTP in this love version can be BUGGY
*** ON X86 EVERYTHINK SHOULD BE FINE but
*** we dont know about x86_64
*** so x86_64 is up-to-you if You want test it
FOR STABLE Release use latest stable version: 2.6.12-rc3-love1
Love-Sources 2.6.12-rc5-love1 "Everest Climbed by Hairdressers"
This is testing_period now , If will be some errors by any other patch
we can reverse it just before final release 
| Code: |
*** In Love-Sources features menu : ***
*** Default Options are SAFE and GOOD working on x86 ***
*** RTP in this love version can be BUGGY ***
*** ON X86 EVERYTHINK SHOULD BE FINE but ***
*** we dont know about x86_64 ***
*** so x86_64 is up-to-you if You want test it ***
!!! ONLY SHORT DESCRIPTIONS OR NAMES ARE IN THIS INFO !!!
!!! YOU CAN LOOK INTO EVERY PATCH CODE OR FULL DESCRIPTION !!!
!!! BY DOWNLOADING OUR SPLIT-OUT FILE !!!
---info------------------------------------------------------------
Please don't report any bugs to gentoo-devs or bugs.gentoo.org.
We are making patchset for x86 .
We will be not able to help You with x86_64
-------------------------------------------------------------------
If You want support or jusk ask about something -
please join #love-sources on freenode or just
post in the love-sources thread in "Unsupported Software" forum on
forums.gentoo.org , check also love-sources.org
-------------------------------------------------------------------
-->> patchlist first <<---
1) base :
realtime-preempt-2.6.12-rc5-V0.7.47-12
>> Ingo Molnar's Real Time Preemption patchset.
>> Default Mode is : "Low Latency Destkop Mode" and Hard/Soft IRQs threadings are disabled
>> Full RT mode isnt required for _overall_ destkop using
>> so we decided to make Low Latency Destkop Mode as defualt love mode.
>> You can now select also FULL RT mode and Hard/Soft IRQs threading
>> in Love-Sources features menu if You want to have really extremaly low latencies
>> but remember this can be occupied in an overall performance decresing cost or
>> by making Your system unstable and by potential bugs risk...
2) io schedulers fixes/updates :
def_iosched_select_menu.diff
>> selectable def.io scheduler from (menu)config
cfq-cfq-elevator_insert_back-fix.patch
cfq-cfq_io_context-leak-fix.patch
cfq-iosched-update-to-time-sliced-design-export-task_nice.patch
cfq-iosched-update-to-time-sliced-design-fix-fix.patch
cfq-iosched-update-to-time-sliced-design-fix.patch
cfq-iosched-update-to-time-sliced-design-use-bio_data_dir.patch
cfq-iosched-update-to-time-sliced-design.patch
cfq-ioschedc-fix-soft-hang-with-non-fs-requests.patch
cfq-remove-serveral-unused-fields-from-cfq-data-structures.patch
>> timeslices design updates and additional fixes for CFQ.
as-limit-queue-depth.patch
>> a small anticipatory improvement.
3) All rest :) :
//Please note that RT-Limits are in rc4 now.
>> for using the RT rlimits patch for Linux Audio : http://www.steamballoon.com/wiki/Rlimits
ext3-reduce-allocate-with-reservation-lock-latencies-tidy.patch
>> ext3 latencies and fixes
>> main ext3 latencies fixes are now directly in RTP
make-reiserfs-bug-on-too-big-transaction.patch
>> Make reiserfs BUG() when somebody tries to start a larger transaction than
>> it's allowed (currently the code just silently deadlocks).
reiserfs-add-checking-of-journal_begin-return-value.patch
git-jfs.patch
git-ntfs.patch
>> up-to-date jfs and ntfs from git
gregkh-04-usb-2.6.12-rc5.patch
>> USB up-to-date from kernel.org and Greg's dir.
configurable-ide-delay.patch
>> You can choose a delay for IDE devices now.
>> default is 50ms. You can try lower it to 5ms
>> and You should have booting time around ~5secs shorter.
>> all new drives should work with this but remember
>> You can do this for own risk , default is 50ms
>> available via love-sources menu
alsa-from-2.6.12-rc5-mm1
>> as in name
rpc-kick-off-socket-connect-operations-faster.patch
>> Make the socket transport kick the event queue to start socket connects
>> immediately. This should improve responsiveness of applications that are
>> sensitive to slow mount operations (like automounters).
add-check-to-proc-devices-read-routines.patch
>> small "security" fix.
avoiding-mmap-fragmentation-fix.patch
avoiding-mmap-fragmentation-revert-unneeded-64-bit-changes.patch
avoiding-mmap-fragmentation-tidy.patch
avoiding-mmap-fragmentation.patch
>> a fix for applications that run out of memory on 2.6 kernels
>> but works on 2.4 after the Ingo speed-up by allocating new mmaps by free_area_cache
fix-agp-code-to-work-again-with-non-pci-agp-bridges.patch
>> exactly as in name :)
__wait_on_freeing_inode-fix.patch
fix-of-dcache-race-leading-to-busy-inodes-on-umount-fix.patch
fix-of-dcache-race-leading-to-busy-inodes-on-umount-tidy.patch
fix-of-dcache-race-leading-to-busy-inodes-on-umount.patch
>> dcache race between shrink_dcache_XXX functions and dput() fixes.
i386-never-block-forced-sigsegv.patch
>> as in name fix :)
o1-sb-list-traversing-on-syncs.patch
>> This patch removes O(n^2) super block loops in sync_inodes(),sync_filesystems() etc.
quiet-ide-cd-warning.patch
>> This shuts up a potential uninitialized variable warning.
avoid-recursive-oopses.patch
>> Prevent recursive faults in do_exit() by leaving the task alone and wait
>> for reboot
improve-cd-dvd-packet-driver-write-performance.patch
>> This patch improves write performance for the CD/DVD packet writing driver.
>> The logic for switching between reading and writing has been changed so
>> that streaming writes are no longer interrupted by read requests.
mempool-only-init-waitqueue-in-slow-path.patch
>> Here's a small patch to improve the performance of mempool_alloc by only
>> initializing the wait queue when we're about to wait.
mystery-ide-fix.patch
>> "the one of the big misterious fixes from all times " :)
properly-stop-devices-before-poweroff-fix.patch
properly-stop-devices-before-poweroff.patch
>> as in name :)
inotify-44-update.patch
inotify-44-warning-fix.patch
inotify-44.patch
>> successor od dnotify ( rc5mm1 )
sched-changing-rt-priority-without-cap_sys_nice.patch
>> Presently, a process without the capability CAP_SYS_NICE can not change
>> its own policy, which is OK.
>> But it can also not decrease its RT priority (if scheduled with policy
>> SCHED_RR or SCHED_FIFO), which is what this patch changes.
>> with this patch, process scheduled by SCHED_FIFO, SCHED_RR and
>> SCHED_OTHER can all decrease their priority.
sched-micro-optimize-task-requeueing-in-schedule.patch
>> micro-optimize task requeueing in schedule() & clean up recalc_task_prio().
libata-2.6.patch
>> up-to-date lib-ata fixes from LKML
__wait_on_freeing_inode-fix.patch
binfmt_elf-bss-padding-fix.patch
>> if an ELF file specifies a zero-length bss at a whacky address,
>> we cannot load that binary because padzero() tries to zero out the end of
>> the page at the whacky address, and that may not be writeable.
quota-consolidate-code-surrounding-vfs_quota_on_mount.patch
quota-ext3-improve-quota-credit-estimates.patch
quota-improve-credits-estimates.patch
quota-reiserfs-improve-quota-credit-estimates.patch
quota-sanitize-dentry-handling-in-vfs_quota_on_mount.patch
>> quota fixes from 2612rc5mm1
vesafb-tng-0.9-rc6-r2-2.6.12-rc1.patch
>> a tool fro setting and controlling vesafb refresh rate.
mapped_watermark3.diff
>> swapping improvement from ck.
1g_lowmem1_i386.diff
>> for users having a lot of memory :)
usbhid-readd-kconfig-r1.patch
>> configuration of usb mouse polling via (menu)config.
logos.diff
>> You can select now booting love-sources logo via love-source features menu.
>> http://vivid.dat.pl/fallow/pub/index.php?dir=love-sources/love-logos/
>> 2 logos fallow-logo1 and sith_happens logo2 ( 2 winners of voting )
|
| FAQ wrote: |
-- Love Sources FAQ --
Q: I have black-sreen freezing after startx
A: Please try compile kernel without vesa-tng support at all.
Q: Why RTP and Ingosched are in Love-Sources now ?
A: Ingosched has greatest testing because is tested for all vanilla users.
It is also defulat Linux 2.6 CPU Scheduler and it is pretty fixed now.
Ingosched developing also doesnt sleep, look into MM tree for example.
RTP is a Ingo Molnar extension to providing a kind of Real Time Preemption.
Default Mode is : "Low Latency Destkop Mode" and Hard/Soft IRQs threadings are disabled
Full RT mode isnt required for _overall_ destkop using
so we decided to make Low Latency Destkop Mode as defualt love mode.
You can now select also FULL RT mode and Hard/Soft IRQs threading
in Love-Sources features menu if You want to have really extremaly low latencies
but remember this can be occupied in an overall performance decresing cost or
by making Your system more unstable...
Q: How to use the RT rlimits patch for Linux Audio ?
A: please follow a nice how-to here -> http://www.steamballoon.com/wiki/Rlimits
Q: So, where did Reiser4 go?
A: Away
Q: Why?
A: A number of reasons, the love sources team strive to bring you the
best desktop experience and Reiser4 can greatly degrades interactivity and
increse cpu usage . It's unlogical to have CPU Scheduler with oriented for reducint
latencies and filesystem with maximal latencies.
It's also operating under several wrong assumptions on things
like page table sizes. Reiser4 also doesn't support architectures
aside x86 nor does it run on the default 4kb stack setting.
Q: So now that love-sources isn't going to support Reiser4 what do I do?
A: Compile one of the great number of Reiser4 enabled kernels, like
Andrew Morton's mm tree, that one is even in portage.
Q: Why are you pulling Reiser4, it's the base of Love-sources?
A: Actually it's not, when love-sources started it was in large part to
research how to allivate the famous music lag bug. A bug that Reiser4
ironically reintroduces.
Q: Okay so I shouldn't use Reiser4, what then?
A: Ext3 with dir_index is a much better/universal filesystem for a desktop in that
it performs nicely and has really good latency. Aside such likable
qualities as stability , it is in developing for "ages" in comparision to Reiser4 
Q: Im an ext3 user , but how can I check or activate dir_index feature ?
A: Please check if You have it in superblock by this line :
1) my_box# tune2fs -l /dev/hdaXY
if You receive line like this one with dir_index :
Filesystem features: has_journal dir_index filetype needs_recovery sparse_super
You have it activated.
if not, please do :
1) tune2fs -O dir_index /dev/hdXY
2a) updatedb
or
2b) e2fsck -D /dev/hdXY
Q: Im a Laptop user, I want to increse my battery life-time, what should I do ?
A: Use JFS as Your filesystem. It has less cpu usage (definitly better than reiserfs/reiser4)
and Your battery lifetime will be incresed even up-to 30% in comparision to reiserfs/reiser4.
In Love-Sources You have up-to-date fixes for it.
Q: OK, Im interested in good interactivity , I can resign from reiser4 for this.
Now Im using other filesystem ( We recommending You ext3+dir_index ).
Which IO Scheduler should I use ?
A: Please try CFQ-TS io scheduler ( default in love-sources ).
This is Completly Fair Queuing IO Scheduler which gives You optimal destkop interactivity
even in heavy filesystem usage.
Q: What about NVIDIA and ATI fixes?
A: In current love there are no any NVIDIA or ATI fixes.
Please use DRIVER side fixes from the net ( many of it here ) .
If You're NVIDIA USER. Many of good fixes are just in GENTOO PORTAGE.
min kernel driver to run this sources is nvidia-kernel-6629-r4
|
| Info/Warning/Support/Bugs wrote: |
Please don't report any bugs to gentoo-devs or bugs.gentoo.org.
We are making patchset for x86 . We will be not able to help You with x86_64 |
check also http://love-sources.org , and vote for our logo
logo-gallery : http://vivid.dat.pl/fallow/pub/index.php?dir=love-sources/love-logos/
patch : http://vivid.dat.pl/fallow/pub/index.php?dir=love-sources/2.6.12-rc5-love1/&file=2.6.12-rc5-love1.bz2
ebuild : http://vivid.dat.pl/fallow/pub/index.php?dir=love-sources/2.6.12-rc5-love1/&file=love-sources-2.6.12_rc5-r1.ebuild (thx Mafteah for the clean-up )
notes : http://vivid.dat.pl/fallow/pub/index.php?dir=love-sources/2.6.12-rc5-love1/&file=notes.txt
all dir : http://vivid.dat.pl/fallow/pub/index.php?dir=love-sources/2.6.12-rc5-love1/
cheers
_________________
"Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard
Last edited by fallow on Fri May 27, 2005 3:33 pm; edited 9 times in total |
|
| Back to top |
|
 |
NiLuJe
Guru
Joined: 06 Nov 2004
Posts: 303
Location: Paris, France
|
| Posted: Fri May 27, 2005 12:27 am Post subject: |
|
|
Yeepeee, compiling First feedback in a couple of minutes
EDIT : Woops, patch URL is wrong in the ebuild, missing the last directory
EDIT Bis : Running fine so far. (LLD) Time to go to bed now ;o) (3.32 am here :/) |
|
| Back to top |
|
|
wing
Tux's lil' helper
Joined: 27 Aug 2002
Posts: 108
Location: Mountain View, CA
|
| Posted: Fri May 27, 2005 4:10 am Post subject: |
|
|
Here is the correct path.
| Code: | | LOVEPV_SRC="http://vivid.dat.pl/fallow/pub/${PN}/${KV}/${KV}.bz2" |
edit: No go on amd64
| Code: | CC arch/x86_64/kernel/nmi.o
arch/x86_64/kernel/nmi.c: In function `nmi_watchdog_tick':
arch/x86_64/kernel/nmi.c:497: error: `cpu' undeclared (first use in this function)
arch/x86_64/kernel/nmi.c:497: error: (Each undeclared identifier is reported only once
arch/x86_64/kernel/nmi.c:497: error: for each function it appears in.)
make[1]: *** [arch/x86_64/kernel/nmi.o] Error 1
make: *** [arch/x86_64/kernel] Error 2 |
I know you don't support amd64, I'm just putting this out there for the people who do use it. |
|
| Back to top |
|
|
fallow
Bodhisattva
Joined: 08 Jan 2004
Posts: 2208
Location: Poland
|
| Posted: Fri May 27, 2005 5:51 am Post subject: |
|
|
| NiLuJe wrote: | | Yeepeee, compiling First feedback in a couple of minutes |
I like this
| NiLuJe wrote: |
EDIT : Woops, patch URL is wrong in the ebuild, missing the last directory |
OK Fixed now new ebuild uploaded sorry
| NiLuJe wrote: |
EDIT Bis : Running fine so far. (LLD) Time to go to bed now ;o) (3.32 am here :/) |
great adn thx for the feedback
| wing wrote: | Here is the correct path.
| Code: | | LOVEPV_SRC="http://vivid.dat.pl/fallow/pub/${PN}/${KV}/${KV}.bz2" |
|
thx , corrected
| wing wrote: |
I know you don't support amd64, I'm just putting this out there for the people who do use it. |
OK , I think this should be not hard to fix
this are LLD or FullRT mode errors ?.
| dice wrote: | | fallow wrote: | but WE OFFICIALY SUPPORTING only x86 , not x86_64
from this point of view, there is no errors on x86.
however , I feel its not enough good . |
What more would you need in order to officialy support x86_64? I can do testing and search LKML for patches then apply and test them. I know C but I've not worked with the kernel and I'm not very familliar with its structure. |
Needs :
1) X86_64 box for testing [ I have x86 ]
2) X86_64 co-maintainer
one of this 2 things.
for patchseting base C knowledge is enough.
I just have not possibilities to test X86_64 modyfications.
You can try to fix existing x86_64 error reported in rc5-love1 thread if You have intend for the beginning
cheers
_________________
"Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard |
|
| Back to top |
|
|
bosyotech
Tux's lil' helper
Joined: 29 Jan 2005
Posts: 79
Location: earth
|
| Posted: Fri May 27, 2005 7:22 am Post subject: |
|
|
hi fallow,
running quite well here but i got an oops when unmounting an ntfs filesystem. i set preemption in FULLLRT, ill try LLD and see it still gives the same oops.
btw, what does that IDE Device Delay option? what impact would it bring if i would set to 5ms as what the docs explain?
_________________
of all the things i've lost, i miss my mind the most |
|
| Back to top |
|
|
playfool
l33t
Joined: 01 Jun 2004
Posts: 688
Location: Ã
rhus, Denmark
|
| Posted: Fri May 27, 2005 7:31 am Post subject: |
|
|
| bosyotech wrote: | hi fallow,
running quite well here but i got an oops when unmounting an ntfs filesystem. i set preemption in FULLLRT, ill try LLD and see it still gives the same oops.
btw, what does that IDE Device Delay option? what impact would it bring if i would set to 5ms as what the docs explain? |
Can you grap the full oops text, so that people can examine it and if possible a step by step guide to reproducing your oops so others might confirm it?
As for the IDE Device Delay, if you have newer hardware it should be able to cope with above specifcation delay times, which means amounts other things a faster boot - now the mere idea of going beyond specs on my IDE driver makes me icky to be honest but some people, namely the ricers, like that sort of breaking goodness that can set their hair on fire and crush their nuts. I really don't recommend it, there are better ways to get around that problem - the only useful scenerio I can imagine for this would be like an embedded platform where you controlled all the hardware, then it would be a good option to speed it up but for the love of <beep> don't do it on a desktop. |
|
| Back to top |
|
|
gringo
Advocate
Joined: 27 Apr 2003
Posts: 3793
|
| Posted: Fri May 27, 2005 7:53 am Post subject: |
|
|
| Quote: | CC arch/x86_64/kernel/nmi.o
arch/x86_64/kernel/nmi.c: In function `nmi_watchdog_tick':
arch/x86_64/kernel/nmi.c:497: error: `cpu' undeclared (first use in this function)
arch/x86_64/kernel/nmi.c:497: error: (Each undeclared identifier is reported only once
arch/x86_64/kernel/nmi.c:497: error: for each function it appears in.)
make[1]: *** [arch/x86_64/kernel/nmi.o] Error 1
make: *** [arch/x86_64/kernel] Error 2 |
get this
cheers |
|
| Back to top |
|
|
bosyotech
Tux's lil' helper
Joined: 29 Jan 2005
Posts: 79
Location: earth
|
| Posted: Fri May 27, 2005 8:21 am Post subject: |
|
|
ok i get this ooops on both FULLRT and LLD both (CFQ-TS) on a P4 2Ghz
1) mount ntfs /mnt/sounds
2) cd /mnt/sounds
3) find -name '*.wav'
4) cd
5) umount /mnt/sounds
Segmentation fault | Code: | May 27 16:04:34 gentoo [ 129.190766] NTFS volume version 3.1.
May 27 16:04:54 gentoo [ 149.143259] BUG at fs/inode.c:1100!
May 27 16:04:54 gentoo [ 149.143306] ------------[ cut here ]------------
May 27 16:04:54 gentoo [ 149.143316] kernel BUG at fs/inode.c:1100!
May 27 16:04:54 gentoo [ 149.143320] invalid operand: 0000 [#1]
May 27 16:04:54 gentoo [ 149.143322] PREEMPT
May 27 16:04:54 gentoo [ 149.143325] Modules linked in: savage drm ohci_hcd parport_pc parport floppy pcspkr savagefb via_rhine mii t
ulip via_agp
May 27 16:04:54 gentoo [ 149.143338] CPU: 0
May 27 16:04:54 gentoo [ 149.143339] EIP: 0060:[<c0179616>] Not tainted VLI
May 27 16:04:54 gentoo [ 149.143341] EFLAGS: 00010292 (2.6.12-rc5-love1)
May 27 16:04:54 gentoo [ 149.143364] EIP is at iput+0xa6/0xc0
May 27 16:04:54 gentoo [ 149.143368] eax: 00000027 ebx: c4aa311c ecx: cd30b040 edx: c037a98c
May 27 16:04:54 gentoo [ 149.143372] esi: c03837e0 edi: c4aa3220 ebp: c4aa311c esp: c4940eb4
May 27 16:04:54 gentoo [ 149.143376] ds: 007b es: 007b ss: 0068 preempt: 00000001
May 27 16:04:54 gentoo [ 149.143379] Process umount (pid: 6798, threadinfo=c4940000 task=cd30b020)
May 27 16:04:54 gentoo [ 149.143382] Stack: c033cd3b c0341c0a 0000044c c4940000 c4aa3220 c0187458 c4aa311c 00000000
May 27 16:04:54 gentoo [ 149.143391] 00000000 00000000 00000000 c4940000 c4aa3228 c4aa311c c4940000 cd397e74
May 27 16:04:54 gentoo [ 149.143399] c4940f08 c4940000 c01784c0 cd397e74 cc2c3100 c4940f08 c4940f08 c523851c
May 27 16:04:54 gentoo [ 149.143407] Call Trace:
May 27 16:04:54 gentoo [ 149.143413] [<c0187458>] inotify_unmount_inodes+0xd8/0x110 (24)
May 27 16:04:54 gentoo [ 149.143434] [<c01784c0>] invalidate_inodes+0x40/0x90 (52)
May 27 16:04:54 gentoo [ 149.143441] [<c0162fbe>] generic_shutdown_super+0x6e/0x160 (32)
May 27 16:04:54 gentoo [ 149.143452] [<c0163d6e>] kill_block_super+0x2e/0x50 (20)
May 27 16:04:54 gentoo [ 149.143457] [<c0162e3b>] deactivate_super+0x5b/0x90 (20)
May 27 16:04:54 gentoo [ 149.143463] [<c017b7ef>] sys_umount+0x3f/0xa0 (20)
May 27 16:04:54 gentoo [ 149.143470] [<c014e60d>] do_munmap+0x11d/0x180 (28)
May 27 16:04:54 gentoo [ 149.143483] [<c014e6b7>] sys_munmap+0x47/0x70 (44)
May 27 16:04:54 gentoo [ 149.143489] [<c017b865>] sys_oldumount+0x15/0x20 (12)
May 27 16:04:54 gentoo [ 149.143495] [<c0102bdb>] sysenter_past_esp+0x54/0x75 (12)
May 27 16:04:54 gentoo [ 149.143506] Code: 83 c4 14 c3 90 89 1c 24 ff 56 14 eb a8 c7 04 24 3b cd 33 c0 b8 4c 04 00 00 89 44 24 08 b8
0a 1c 34 c0 89 44 24 04 e8 5a f5 f9 ff <0f> 0b 4c 04 0a 1c 34 c0 e9 72 ff ff ff 8d b6 00 00 00 00 8d bc
May 27 16:04:54 gentoo [ 149.143546] umount/6798: BUG in do_exit at kernel/exit.c:785
May 27 16:04:54 gentoo [ 149.143552] [<c011b2a3>] do_exit+0x323/0x450 (8)
May 27 16:04:54 gentoo [ 149.143565] [<c0104310>] do_invalid_op+0x0/0xb0 (40)
May 27 16:04:54 gentoo [ 149.143572] [<c0103f8e>] die+0x17e/0x180 (8)
May 27 16:04:54 gentoo [ 149.143580] [<c01043b6>] do_invalid_op+0xa6/0xb0 (60)
May 27 16:04:54 gentoo [ 149.143588] [<c0179616>] iput+0xa6/0xc0 (76)
May 27 16:04:54 gentoo [ 149.143593] [<c0118f82>] release_console_sem+0xd2/0xe0 (20)
May 27 16:04:54 gentoo [ 149.143600] [<c0118d07>] vprintk+0x177/0x280 (32)
May 27 16:04:54 gentoo [ 149.143607] [<c01d9b87>] ntfs_destroy_big_inode+0x37/0xc0 (56)
May 27 16:04:54 gentoo [ 149.143624] [<c0103757>] error_code+0x4f/0x54 (16)
May 27 16:04:54 gentoo [ 149.143631] [<c0179616>] iput+0xa6/0xc0 (44)
May 27 16:04:54 gentoo [ 149.143637] [<c0187458>] inotify_unmount_inodes+0xd8/0x110 (32)
May 27 16:04:54 gentoo [ 149.143645] [<c01784c0>] invalidate_inodes+0x40/0x90 (52)
May 27 16:04:54 gentoo [ 149.143651] [<c0162fbe>] generic_shutdown_super+0x6e/0x160 (32)
May 27 16:04:54 gentoo [ 149.143658] [<c0163d6e>] kill_block_super+0x2e/0x50 (20)
May 27 16:04:54 gentoo [ 149.143664] [<c0162e3b>] deactivate_super+0x5b/0x90 (20)
May 27 16:04:54 gentoo [ 149.143670] [<c017b7ef>] sys_umount+0x3f/0xa0 (20)
May 27 16:04:54 gentoo [ 149.143676] [<c014e60d>] do_munmap+0x11d/0x180 (28)
May 27 16:04:54 gentoo [ 149.143684] [<c014e6b7>] sys_munmap+0x47/0x70 (44)
May 27 16:04:54 gentoo [ 149.143690] [<c017b865>] sys_oldumount+0x15/0x20 (12)
May 27 16:04:54 gentoo [ 149.143696] [<c0102bdb>] sysenter_past_esp+0x54/0x75 (12) |
dunno if someone else got this on 2.6.12-rc5-love1. but on 2.6.12-rc3-love1 very stable.
[edit] btw ntfs on step one is /dev/hdc6 for clarity
_________________
of all the things i've lost, i miss my mind the most |
|
| Back to top |
|
|
gimpel
Advocate
Joined: 15 Oct 2004
Posts: 2720
Location: Munich, Bavaria
|
| Posted: Fri May 27, 2005 8:47 am Post subject: |
|
|
strange, my ntfs /mnt/windoof mounted w/o errors
[edit] oh, your segv is on umount...
i get a little call trace with hald in LLD, didn't try full preempt:
| Code: | May 30 11:26:52 SiRiUS kernel: c019a60d
May 30 11:26:52 SiRiUS kernel: PREEMPT
May 30 11:26:52 SiRiUS kernel: Modules linked in: snd_via82xx it821x
May 30 11:26:52 SiRiUS kernel: CPU: 0
May 30 11:26:52 SiRiUS kernel: EIP: 0060:[check_perm+189/592] Not tainted VLI
May 30 11:26:52 SiRiUS kernel: EIP: 0060:[<c019a60d>] Not tainted VLI
May 30 11:26:52 SiRiUS kernel: EFLAGS: 00010202 (2.6.12-rc5-love1)
May 30 11:26:52 SiRiUS kernel: EIP is at check_perm+0xbd/0x250
May 30 11:26:52 SiRiUS kernel: eax: 000a2a70 ebx: c056fecc ecx: daf1dce0 edx: daf1dc00
May 30 11:26:52 SiRiUS kernel: esi: 00000001 edi: dd010000 ebp: dfc095f8 esp: dd011efc
May 30 11:26:52 SiRiUS kernel: ds: 007b es: 007b ss: 0068 preempt: 00000001
May 30 11:26:52 SiRiUS kernel: Process hald (pid: 9800, threadinfo=dd010000 task=df623060)
May 30 11:26:52 SiRiUS kernel: Stack: dfc095f8 00000000 00000000 daf1dce0 de1ae69c dffe73e0 00000001 c015acc0
May 30 11:26:52 SiRiUS kernel: de1ae69c daf1dce0 00000000 00000000 080ea2c0 0000000e dd010000 c015aadc
May 30 11:26:52 SiRiUS kernel: deaf7d34 dffe73e0 00000000 dd011f4c deaf7d34 dffe73e0 00000003 c0166f91
May 30 11:26:52 SiRiUS kernel: Call Trace:
May 30 11:26:52 SiRiUS kernel: [dentry_open+464/624] dentry_open+0x1d0/0x270 (32)
May 30 11:26:52 SiRiUS kernel: [<c015acc0>] dentry_open+0x1d0/0x270 (32)
May 30 11:26:52 SiRiUS kernel: [filp_open+92/112] filp_open+0x5c/0x70 (32)
May 30 11:26:52 SiRiUS kernel: [<c015aadc>] filp_open+0x5c/0x70 (32)
May 30 11:26:52 SiRiUS kernel: [sys_stat64+49/64] sys_stat64+0x31/0x40 (32)
May 30 11:26:52 SiRiUS kernel: [<c0166f91>] sys_stat64+0x31/0x40 (32)
May 30 11:26:52 SiRiUS kernel: [get_unused_fd+44/224] get_unused_fd+0x2c/0xe0 (28)
May 30 11:26:52 SiRiUS kernel: [<c015ad8c>] get_unused_fd+0x2c/0xe0 (28)
May 30 11:26:52 SiRiUS kernel: [sys_open+91/256] sys_open+0x5b/0x100 (28)
May 30 11:26:52 SiRiUS kernel: [<c015af7b>] sys_open+0x5b/0x100 (28)
May 30 11:26:52 SiRiUS kernel: [sysenter_past_esp+84/117] sysenter_past_esp+0x54/0x75 (40)
May 30 11:26:52 SiRiUS kernel: [<c0102c6b>] sysenter_past_esp+0x54/0x75 (40)
May 30 11:26:52 SiRiUS kernel: Code: 00 ff 80 00 01 00 00 b8 00 e0 ff ff 21 e0 ff 48 14 8b 40 08 a8 08 0f 85 67 01 00 00 85 f6 0f 84 aa 00 00 00 8b 45 28 85 c0 74 07 <8b> 40 04 85 c0 75 0c 8b 45 2c be e0 be 51 c0 85 c0 74 07 8b 70
|
but after that:
| Quote: | /etc/init.d/hald status
* status: started |
other than that: runs good
_________________
http://proaudio.tuxfamily.org/wiki - pro-audio software overlay
|
|
| Back to top |
|
|
fallow
Bodhisattva
Joined: 08 Jan 2004
Posts: 2208
Location: Poland
|
| Posted: Fri May 27, 2005 9:07 am Post subject: |
|
|
ok stop posting this error , Im working on it
RTP is uptaded from 09 to 10 now ( x86_64 compilation error also )
I will back with new version ( fixed )
cheers.
_________________
"Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard |
|
| Back to top |
|
|
fallow
Bodhisattva
Joined: 08 Jan 2004
Posts: 2208
Location: Poland
|
| Posted: Fri May 27, 2005 10:27 am Post subject: |
|
|
OK FIXING DONE
[ 27.05.2005] *** UPDATE 01 - > RTP from 09 to 10 ( THX Gringo for the fast info )
[ 27.05.2005] *** UPDATE 02 - > inotify-44-update-2.patch kicked out ( oops ) now is ok
actual size & md5 | Code: | | MD5 35cc28b814e6f4f523c06b58a7e8f900 2.6.12-rc5-love1.bz2 53840 |
ebuild & patch has the same names. so You have to remove existing patch from /usr/portage/distfiles
remove existing digest from Your portage_overlay directory , and generate it / downlaod the patch again .
now should be without errors
cheers
_________________
"Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard |
|
| Back to top |
|
|
vipernicus
Veteran
Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.
|
| Posted: Fri May 27, 2005 12:37 pm Post subject: |
|
|
Low Latency Desktop Mode doesn't work well for me, I tried FullRT, and I'm impressed, it is very fast and stable on my system. Don't really see any performance loss really.
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog |
|
| Back to top |
|
|
ashtophet
Guru
Joined: 08 Aug 2004
Posts: 397
|
| Posted: Fri May 27, 2005 1:18 pm Post subject: |
|
|
Trying FullRT... wow! seems impressive... awesome interactivity... let's test
cheers |
|
| Back to top |
|
|
fallow
Bodhisattva
Joined: 08 Jan 2004
Posts: 2208
Location: Poland
|
| Posted: Fri May 27, 2005 3:31 pm Post subject: |
|
|
nice to hear this
btw. I did RTP update in this love. new version available in the same dir - > UpdateO3
RTP 10 -->> RTP 12
if sb want only a diff , from RTP10 to RTP12 - > http://vivid.dat.pl/fallow/rtp10_to_12.diff
cheers
_________________
"Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard |
|
| Back to top |
|
|
gimpel
Advocate
Joined: 15 Oct 2004
Posts: 2720
Location: Munich, Bavaria
|
| Posted: Fri May 27, 2005 3:45 pm Post subject: |
|
|
/me passes fallow an icecold beer!
running up02 atm, very nice! knocking in in the new diff now, hehe
thx once more for the good work, man
_________________
http://proaudio.tuxfamily.org/wiki - pro-audio software overlay
|
|
| Back to top |
|
|
bosyotech
Tux's lil' helper
Joined: 29 Jan 2005
Posts: 79
Location: earth
|
| Posted: Sat May 28, 2005 1:11 am Post subject: |
|
|
thank you very much fallow. /me hands fallow a very sexy blonde lady holding an ice cold beer saying | sexy blonde wrote: | i love it when you update things  |
_________________
of all the things i've lost, i miss my mind the most |
|
| Back to top |
|
|
vipernicus
Veteran
Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.
|
| Posted: Sat May 28, 2005 1:40 am Post subject: |
|
|
Couple of small probs.
Desktop Mode won't compile.
In FullRT:
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
BUG: Unable to handle kernel paging request at virtual address 000a2a74
printing eip:
c01980c4
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
Modules linked in:
CPU: 0
EIP: 0060:[<c01980c4>] Not tainted VLI
EFLAGS: 00010202 (2.6.12-rc5-love1)
eax: 000a2a70 ebx: c04653ac ecx: 00000001 edx: 00000000
esi: 00000001 edi: eec49380 ebp: efd2e3b8 esp: ef34def0
ds: 007b es: 007b ss: 0068 preempt: 00000001
Process hald (pid: 3300, threadinfo=ef34d000 task=eee68660)
Stack: c0410560 c013541a c040fa20 00000001 c015c767 00000000 eec49380 ee7bbc04
c16ed500 00000001 c015c899 ee7bbc04 eec49380 0810a0c2 00000000 0810a510
0000000d ef34d000 c015c6c6 eecc2040 c16ed500 00000000 ef34df4c eecc2040
Call Trace:
[<c013541a>] up_mutex+0x81/0x108 (
[<c015c767>] dentry_open+0x9c/0x26c (12)
[<c015c899>] dentry_open+0x1ce/0x26c (24)
[<c015c6c6>] filp_open+0x5c/0x61 (32)
[<c015c9e2>] get_unused_fd+0xab/0xd3 (32)
[<c015c9e2>] get_unused_fd+0xab/0xd3 (24)
[<c015cb39>] sys_open+0x5b/0xff (32)
[<c0103003>] sysenter_past_esp+0x54/0x75 (40)
Code: ff 82 00 01 00 00 b8 00 f0 ff ff 21 e0 83 68 14 01 8b 40 08 a8 08 0f 85 5$
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog |
|
| Back to top |
|
|
fallow
Bodhisattva
Joined: 08 Jan 2004
Posts: 2208
Location: Poland
|
| Posted: Sat May 28, 2005 6:59 am Post subject: |
|
|
| gimpel wrote: | /me passes fallow an icecold beer!
running up02 atm, very nice! knocking in in the new diff now, hehe
thx once more for the good work, man |
hehe thanx welcome
| bosyotech wrote: | thank you very much fallow. /me hands fallow a very sexy blonde lady holding an ice cold beer saying | sexy blonde wrote: | | i love it when you update things |
|
is this Pamela ? I please Halle Berry also thx man
vipernicus :
about FullRT
| Lovechild & Fallow wrote: |
realtime-preempt-2.6.12-rc5-V0.7.47-12
>> Ingo Molnar's Real Time Preemption patchset.
>> Default Mode is : "Low Latency Destkop Mode" and Hard/Soft IRQs threadings are disabled
>> Full RT mode isnt required for _overall_ destkop using
>> so we decided to make Low Latency Destkop Mode as defualt love mode.
>> You can now select also FULL RT mode and Hard/Soft IRQs threading
>> in Love-Sources features menu if You want to have really extremaly low latencies
>> but remember this can be occupied in an overall performance decresing cost or
>> by making Your system unstable and by potential bugs risk...
|
FullRT is just risky and experimental. on some machines ( the slower for example ) You can feel sometimes for example soud skipping, all IRQs in FullRT are threaded to processes.
LLD mode is stable, and we recommending it and this is default setting, if You are brave , You can try FullRT.
but Im not Ingo Molnar , please dont report bugs releted _directly_ to FullRT here, better is to do :
1) test the same bug on vanilla+RTP
2) report this bug to LKML and/or to Ingo Molnar , the maintainer of RTP patchset.
of course all LLD bugs are very welcome, we recomending this mode and we want to have it stable on our patchset.
cheers.
_________________
"Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard |
|
| Back to top |
|
|
Meqif
Tux's lil' helper
Joined: 09 Mar 2003
Posts: 103
Location: Portugal
|
| Posted: Sat May 28, 2005 9:36 am Post subject: |
|
|
I'm having the exact same problem gimpel has:
| Code: | BUG: Unable to handle kernel paging request at virtual address 30706936
printing eip:
c019115a
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
Modules linked in: ehci_hcd uhci_hcd usbcore nvidia
CPU: 0
EIP: 0060:[<c019115a>] Tainted: P VLI
EFLAGS: 00010202 (2.6.12-rc5-love1)
EIP is at check_perm+0xc1/0x236
eax: 30706932 ebx: e15873cc ecx: dd008180 edx: dd008100
esi: 00000001 edi: dbfc2000 ebp: dc03fdb8 esp: dbfc3efc
ds: 007b es: 007b ss: 0068 preempt: 00000001
Process hald (pid: 16413, threadinfo=dbfc2000 task=d77c1a60)
Stack: dc03fdb8 00000000 00000000 dd008180 dc5895a0 dffe3a00 00000001 c0155cb6
dc5895a0 dd008180 00001000 00000000 080e6d28 0000000e dbfc2000 c0155ae9
d8ea31ec dffe3a00 00000000 dbfc3f4c d8ea31ec dffe3a00 00000003 c01615ef
Call Trace:
[<c0155cb6>] dentry_open+0x1c8/0x266 (32)
[<c0155ae9>] filp_open+0x5c/0x61 (32)
[<c01615ef>] sys_stat64+0x31/0x36 (32)
[<c0155d80>] get_unused_fd+0x2c/0xd2 (28)
[<c0155f4f>] sys_open+0x5b/0xff (28)
[<c01029bf>] sysenter_past_esp+0x54/0x75 (40)
Code: ff 80 00 01 00 00 b8 00 e0 ff ff 21 e0 83 68 14 01 8b 40 08 a8 08 0f 85 5d 01 00 00 85 f6 0f 84 a6 00 00 00 8b 45 28 85 c0 74 07 <8b> 40 04 85 c0 75 0c 8b 45 2c be 80 c6 41 c0 85 c0 74 07 8b 70 |
I'm also using LLD. |
|
| Back to top |
|
|
fallow
Bodhisattva
Joined: 08 Jan 2004
Posts: 2208
Location: Poland
|
| Posted: Sat May 28, 2005 9:47 am Post subject: |
|
|
this is impossible
do U using new updated version with kickout out inotyfi-fix-2.patch ?
gimpel's and rest ( mine also ) oops was becuase of this patch.now its kicked out .
so this patch | Code: | | 2.6.12-rc5-love1.bz2 567846 bytes |
?
when do U receiving this oops ?
cheers.
_________________
"Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard
Last edited by fallow on Sat May 28, 2005 10:13 am; edited 1 time in total |
|
| Back to top |
|
|
Meqif
Tux's lil' helper
Joined: 09 Mar 2003
Posts: 103
Location: Portugal
|
| Posted: Sat May 28, 2005 9:55 am Post subject: |
|
|
Yeah, I thought it's pretty weird I'm having this error, but I checked now the file and got this:
| Code: | root@envy:: ls -lb /usr/portage/distfiles/2.6.12-rc5-love1.bz2 [meqif]
-rw-rw-r-- 1 root portage 567846 Mai 27 16:20 /usr/portage/distfiles/2.6.12-rc5-love1.bz2
root@envy:: md5sum /usr/portage/distfiles/2.6.12-rc5-love1.bz2 [meqif]
29cc3fd371ef717ade79c4e86a2de5e4 /usr/portage/distfiles/2.6.12-rc5-love1.bz2 |
Which means I have the latest version (update 03), right?
I get this oops after starting hald, be it while booting or when the system is up.
Thanks for the quick reply.
EDIT: I'll remerge it, sometimes this voodoo helps. |
|
| Back to top |
|
|
fallow
Bodhisattva
Joined: 08 Jan 2004
Posts: 2208
Location: Poland
|
|
| Back to top |
|
|
Meqif
Tux's lil' helper
Joined: 09 Mar 2003
Posts: 103
Location: Portugal
|
| Posted: Sat May 28, 2005 11:06 am Post subject: |
|
|
I reversed all inotify patches (inotify-44.patch, inotify-44-update.patch, inotify-44-warning-fix.patch and inotify-44-update-2.patch) but I'm still getting the oops. 
Thanks for your time. |
|
| Back to top |
|
|
fallow
Bodhisattva
Joined: 08 Jan 2004
Posts: 2208
Location: Poland
|
| Posted: Sat May 28, 2005 12:28 pm Post subject: |
|
|
| Meqif wrote: | I reversed all inotify patches (inotify-44.patch, inotify-44-update.patch, inotify-44-warning-fix.patch and inotify-44-update-2.patch) but I'm still getting the oops.
Thanks for your time. |
no problem
what about pure vanilla+RTP or pure vanilla ?
cheers.
_________________
"Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard |
|
| Back to top |
|
|
Dark_Cloud
n00b
Joined: 29 Jun 2003
Posts: 27
|
| Posted: Sat May 28, 2005 1:20 pm Post subject: |
|
|
| fallow wrote: |
FullRT is just risky and experimental. on some machines ( the slower for example ) You can feel sometimes for example soud skipping, all IRQs in FullRT are threaded to processes.
LLD mode is stable, and we recommending it and this is default setting, if You are brave , You can try FullRT.
but Im not Ingo Molnar , please dont report bugs releted _directly_ to FullRT here, better is to do :
1) test the same bug on vanilla+RTP
2) report this bug to LKML and/or to Ingo Molnar , the maintainer of RTP patchset.
of course all LLD bugs are very welcome, we recomending this mode and we want to have it stable on our patchset.
cheers. |
What is FULL RT? And what are the differences between a Full RT Desktop and a Low Latency one?
thank u |
|
| Back to top |
|
|
|
Unsupported Software
