Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[ release_cancelled ] 2.6.12-rc4-love1
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
fallow
Bodhisattva
Bodhisattva


Joined: 08 Jan 2004
Posts: 2206
Location: Poland

PostPosted: Sun May 15, 2005 9:18 pm    Post subject: [ release_cancelled ] 2.6.12-rc4-love1 Reply with quote


currently this is testing version , not official release.
If everythings will be ok , it will be marked as official release.


Love-Sources 2.6.12-rc4-love1 "Nobody expects the Spanish Inquisition!"

This is testing_period now , If will be some errors by alsa-bk,git-ntfs or block-dev fixes or any other patch
we can reverse it just before final release :)

Code:

-->> patchlist first <<---
1) base :
realtime-preempt-2.6.12-rc4-V0.7.47-03
   >> Ingo Molnar's Real Time Preemption patchset.
   >> Full RT mode is disabled, also disabled are Soft/Hard IRQs threading.
   >> Default Mode is : "Low Latency Destkop Mode"
   >> Full RT mode isnt required for destkop using, and can make more negatives than positives,
   >> in overall destkop using acpect.
   >> so we decided to make Low Latency Destkop Mode as defualt love mode.

2) io schedulers fixes/updates :
def_iosched_select_menu.diff
   >> selectable def.io scheduler from (menu)config
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-plus-rtp-inotify-remount-oops-lovechilds-fix.diff
   >> timeslices design updates and additional fixes for CFQ.
as-limit-queue-depth.patch
   >> a small anticipatory improvement.

3) filesystems/block dev improvements/fixes :
ext3-reduce-allocate-with-reservation-lock-latencies-tidy.patch
ext3-reduce-allocate-with-reservation-lock-latencies.patch
   >> ext3 latencies and fixes.

//Please note that other fixes from our previous release
//(rest of ext3 fixes and reiserfs) are now included in rc4.

blk-__make_request-efficiency.patch
blk-branch-hints.patch
blk-cleanup-generic-tag-support-error-messages.patch
blk-fastpath-get_request.patch
blk-light-iocontext-ops.patch
blk-no-memory-barrier.patch
blk-reduce-locking-fixes.patch
blk-reduce-locking.patch
blk-remove-blk_queue_tag-real_max_depth-optimization.patch
blk-remove-blk_tags_per_longmask.patch
blk-unplug-later.patch
blk-use-find_first_zero_bit-in-blk_queue_start_tag.patch
   >> a lot of ll_rw_blk.c fixes and new solutions
   >> mostly by Nick Piggin and Tejun Heo

4) 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

logos.diff
   >> You can select now booting love-sources logo via love-source features menu.
   >> The selection is beetwen all logos in gallery :
   >> http://vivid.dat.pl/fallow/pub/index.php?dir=love-sources/love-logos/
alsa-series-from-2.6.12-rc4-mm1
   >> all ALSA patches from Andrew Morton's tree
git-ntfs.patch
   >> git ntfs as in name
git-jfs.patch
   >> git jfs as in name
add-check-to-proc-devices-read-routines.patch
   >> small "security" fix.
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
do_swap_page-can-map-random-data-if-swap-read-fails.patch
   >> do_swap_page(); bug fix
fix-agp-code-to-work-again-with-non-pci-agp-bridges.patch
   >> exactly as in name :)
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.
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.
support-for-dx-directories-in-ext3_get_parent-nfsd.patch
   >> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=3D150759 and           
   >> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=3D144556
unplug-can-sleep.patch
   >> adding a might_sleep(); to generic_unplug_device in ll_rw_blk.
500-sched_tunables.txt
   >> (from MJB) a little bit ricer patch but interesting because
   >> You can have fun now by controlling Ingoscheduler via /proc/sys/sched parameters.
inotify-0.23-rml-2.6.12-rc4-7.patch
   >> successor od dnotify.
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.
cddvd-cmdfilter-drop.patch
   >> non-root users cd hack 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.

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.
Full RT mode isnt required for overall desktop using and can even make lags or worst
overall interactivity. We decided to provide "Low Latency Desktop Mode" from Ingo pack
as defulat Preemption Level.Full RT isnt available via love-sources menuconfig.
Soft and Hard IRQ Threading are also disabled.

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 ;)


patch : http://vivid.dat.pl/fallow/pub/index.php?dir=love-sources/2.6.12-rc4-love1/&file=2.6.12-rc4-love1.bz2
ebuild : http://vivid.dat.pl/fallow/pub/index.php?dir=love-sources/2.6.12-rc4-love1/&file=love-sources-2.6.12_rc4-r1.ebuild
notes : http://vivid.dat.pl/fallow/pub/index.php?dir=love-sources/2.6.12-rc4-love1/&file=notes.txt

all dir : http://vivid.dat.pl/fallow/pub/index.php?dir=love-sources/2.6.12-rc4-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 Tue May 17, 2005 7:14 pm; edited 4 times in total
Back to top
View user's profile Send private message
priestjim
Tux's lil' helper
Tux's lil' helper


Joined: 09 Jan 2005
Posts: 100
Location: Never never land

PostPosted: Mon May 16, 2005 1:13 am    Post subject: Reply with quote

Testing right now. Really hope you publish the patchset broken out (I am making one and I like some of your patches) :)
_________________
My soul is my antenna, I am the instrument + the guitar is my amplifier.
-- Ottmar Liebert
Back to top
View user's profile Send private message
vipernicus
Veteran
Veteran


Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.

PostPosted: Mon May 16, 2005 4:39 am    Post subject: Reply with quote

fallow,
what are the pros and cons of compiling with 4k stacks?
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog
Back to top
View user's profile Send private message
playfool
l33t
l33t


Joined: 01 Jun 2004
Posts: 688
Location: Århus, Denmark

PostPosted: Mon May 16, 2005 9:25 am    Post subject: Reply with quote

vipernicus wrote:
fallow,
what are the pros and cons of compiling with 4k stacks?


I'll take that:
http://lwn.net/Articles/84583/
Back to top
View user's profile Send private message
pwe
Guru
Guru


Joined: 12 Mar 2005
Posts: 445
Location: Polska aka Poland

PostPosted: Mon May 16, 2005 9:42 am    Post subject: Reply with quote

Quote:
Info/Warning/Support/Bugs napisa³:

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 ;)

:cry:
but on my Arch Linux system rc3-love1 working fine :)
Back to top
View user's profile Send private message
fallow
Bodhisattva
Bodhisattva


Joined: 08 Jan 2004
Posts: 2206
Location: Poland

PostPosted: Mon May 16, 2005 9:59 am    Post subject: Reply with quote

pwe wrote:
Quote:
Info/Warning/Support/Bugs napisa³:

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 ;)

:cry:
but on my Arch Linux system rc3-love1 working fine :)


and rc4-love1 not ? :)

in rc3-love1 thread we wrote the same info about x86 and x86_64.
We just dont have possibilities to testing it on x86_64.

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
View user's profile Send private message
pwe
Guru
Guru


Joined: 12 Mar 2005
Posts: 445
Location: Polska aka Poland

PostPosted: Mon May 16, 2005 10:26 am    Post subject: Reply with quote

really? ok i will test it on gentoo today/tomorow. i will write :) thanks
Back to top
View user's profile Send private message
fallow
Bodhisattva
Bodhisattva


Joined: 08 Jan 2004
Posts: 2206
Location: Poland

PostPosted: Mon May 16, 2005 10:33 am    Post subject: Reply with quote

pwe wrote:
really? ok i will test it on gentoo today/tomorow. i will write :) thanks


no problem. I corrected small menuconfig error for x86_64 :)

thanks to chaosite for reporting this bug :)

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
View user's profile Send private message
pwe
Guru
Guru


Joined: 12 Mar 2005
Posts: 445
Location: Polska aka Poland

PostPosted: Mon May 16, 2005 11:41 am    Post subject: Reply with quote

quick news: on my Arch 32bit with the 'rc3-love1 config' I cant compile it
Code:
  GEN     .version
  CHK     include/linux/compile.h
  UPD     include/linux/compile.h
  CC      init/version.o
  LD      init/built-in.o
  LD      .tmp_vmlinux1
kernel/built-in.o(.text+0x557): In function `try_to_wake_up':
: undefined reference to `__trace_start_sched_wakeup'
kernel/built-in.o(.text+0x7c9): In function `wake_up_new_task':
: undefined reference to `__trace_start_sched_wakeup'
kernel/built-in.o(.text+0x9f2): In function `schedule_tail':
: undefined reference to `trace_stop_sched_switched'
kernel/built-in.o(.sched.text+0x393): In function `__schedule':
: undefined reference to `trace_stop_sched_switched'
kernel/built-in.o(.sched.text+0x5a9): In function `__schedule':
: undefined reference to `trace_stop_sched_switched'
kernel/built-in.o(.data+0x768): undefined reference to `wakeup_timing'
make: *** [.tmp_vmlinux1] B³±d 1

fu** i dont have time to check it now :/ later
Back to top
View user's profile Send private message
vipernicus
Veteran
Veteran


Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.

PostPosted: Mon May 16, 2005 12:40 pm    Post subject: Reply with quote

pwe wrote:
quick news: on my Arch 32bit with the 'rc3-love1 config' I cant compile it
Code:
  GEN     .version
  CHK     include/linux/compile.h
  UPD     include/linux/compile.h
  CC      init/version.o
  LD      init/built-in.o
  LD      .tmp_vmlinux1
kernel/built-in.o(.text+0x557): In function `try_to_wake_up':
: undefined reference to `__trace_start_sched_wakeup'
kernel/built-in.o(.text+0x7c9): In function `wake_up_new_task':
: undefined reference to `__trace_start_sched_wakeup'
kernel/built-in.o(.text+0x9f2): In function `schedule_tail':
: undefined reference to `trace_stop_sched_switched'
kernel/built-in.o(.sched.text+0x393): In function `__schedule':
: undefined reference to `trace_stop_sched_switched'
kernel/built-in.o(.sched.text+0x5a9): In function `__schedule':
: undefined reference to `trace_stop_sched_switched'
kernel/built-in.o(.data+0x768): undefined reference to `wakeup_timing'
make: *** [.tmp_vmlinux1] B³±d 1

fu** i dont have time to check it now :/ later


If you opened up Arch's testing repository, and did a pacman -Syu, you will have gcc 4.0 and the glibc 2.3.5. Did you do this by any chance?
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog
Back to top
View user's profile Send private message
fallow
Bodhisattva
Bodhisattva


Joined: 08 Jan 2004
Posts: 2206
Location: Poland

PostPosted: Mon May 16, 2005 1:00 pm    Post subject: Reply with quote

pwe wrote:
quick news: on my Arch 32bit with the 'rc3-love1 config' I cant compile it
Code:
  GEN     .version
  CHK     include/linux/compile.h
  UPD     include/linux/compile.h
  CC      init/version.o
  LD      init/built-in.o
  LD      .tmp_vmlinux1
kernel/built-in.o(.text+0x557): In function `try_to_wake_up':
: undefined reference to `__trace_start_sched_wakeup'
kernel/built-in.o(.text+0x7c9): In function `wake_up_new_task':
: undefined reference to `__trace_start_sched_wakeup'
kernel/built-in.o(.text+0x9f2): In function `schedule_tail':
: undefined reference to `trace_stop_sched_switched'
kernel/built-in.o(.sched.text+0x393): In function `__schedule':
: undefined reference to `trace_stop_sched_switched'
kernel/built-in.o(.sched.text+0x5a9): In function `__schedule':
: undefined reference to `trace_stop_sched_switched'
kernel/built-in.o(.data+0x768): undefined reference to `wakeup_timing'
make: *** [.tmp_vmlinux1] B³±d 1

fu** i dont have time to check it now :/ later


PLEASE DEACTIVATE
[ ] Wakeup latency timing
[ ] Non-preemptible critical section latency timing

in Kernel Hacking menu.

I must do correction for it, new patch will be uploaded soon to vivid.dat.pl :)


OK , fixed release is uploaded to vivid.dat.pl , patch has the same name :)
97c38197ee338494198de2d28177a37e 2.6.12-rc4-love1.bz2
357209bytes <-> 2.6.12-rc4-love1.bz2


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
View user's profile Send private message
lucke
n00b
n00b


Joined: 11 May 2005
Posts: 35

PostPosted: Mon May 16, 2005 2:11 pm    Post subject: Reply with quote

Hym, I must report that my sound (via82xx) started to quirk occasionally after installing this kernel, due to the alsa mm patches, I presume.
Back to top
View user's profile Send private message
vipernicus
Veteran
Veteran


Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.

PostPosted: Mon May 16, 2005 2:35 pm    Post subject: Reply with quote

Which performs better for you guys, Ingo Low Latency Desktop or Staircase? I still get better performance, with 2.6.12-rc4 patched with ck, a few mm patches, and cfq-ts.
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog
Back to top
View user's profile Send private message
playfool
l33t
l33t


Joined: 01 Jun 2004
Posts: 688
Location: Århus, Denmark

PostPosted: Mon May 16, 2005 3:49 pm    Post subject: Reply with quote

vipernicus wrote:
Which performs better for you guys, Ingo Low Latency Desktop or Staircase? I still get better performance, with 2.6.12-rc4 patched with ck, a few mm patches, and cfq-ts.


Ingosched + RTP Low latency desktop works very nicely for me, I haven't tried the very latest staircase which Con says contain an important fix.
Back to top
View user's profile Send private message
vipernicus
Veteran
Veteran


Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.

PostPosted: Mon May 16, 2005 3:52 pm    Post subject: Reply with quote

playfool wrote:
vipernicus wrote:
Which performs better for you guys, Ingo Low Latency Desktop or Staircase? I still get better performance, with 2.6.12-rc4 patched with ck, a few mm patches, and cfq-ts.


Ingosched + RTP Low latency desktop works very nicely for me, I haven't tried the very latest staircase which Con says contain an important fix.


You should give it a try, it works very well.
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog
Back to top
View user's profile Send private message
pwe
Guru
Guru


Joined: 12 Mar 2005
Posts: 445
Location: Polska aka Poland

PostPosted: Mon May 16, 2005 4:30 pm    Post subject: Reply with quote

[quote="vipernicus"]
pwe wrote:

If you opened up Arch's testing repository, and did a pacman -Syu, you will have gcc 4.0 and the glibc 2.3.5. Did you do this by any chance?


No i didnt :) when gcc will by in stable repo i'll download it then :)

thanks fallow!! with 'new' patch and without this options in kernel hacking menu:
Code:
 [ ] Wakeup latency timing
[ ] Non-preemptible critical section latency timing

IT WORKS !! :wink:

thanks!!!!

ps i have few minutes now, so im going to gentoo and try to apply this patch on 64bits.
ps2 if someone wants PKGBUILD for this sources -> PM :wink:
Back to top
View user's profile Send private message
vipernicus
Veteran
Veteran


Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.

PostPosted: Mon May 16, 2005 5:42 pm    Post subject: Reply with quote

fallow,
one of your patches is causing me trouble, don't know which one. while in a custom patchset of my own: 2.6.12-rc4-ck1, ext3 -mm fixes, new cfq-ts, I moved 20 gigs of data from one hard drive /multimedia to another on /home/user/multi-backup. Took quite a while, but no problems. Installed your new patchset. changed /multimedia from reiser3.6 to ext3 with full journalling, and set them to move back. went to work, and came back from lunch to find that I had a fatal IO error, it looked like my /home or / had been unmounted. i had to reboot into my own custom ck, and have set the files to move, and have had no problems so far.
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog
Back to top
View user's profile Send private message
pwe
Guru
Guru


Joined: 12 Mar 2005
Posts: 445
Location: Polska aka Poland

PostPosted: Mon May 16, 2005 6:09 pm    Post subject: Reply with quote

anyone compiled this patchset for amd64? i started few minutes ago and after 10sec it fails. ????

my errors:
Code:
 LD      arch/x86_64/kernel/intel_cacheinfo.o
  LD      arch/x86_64/kernel/built-in.o
  CC      arch/x86_64/kernel/head64.o
  CC      arch/x86_64/kernel/init_task.o
arch/x86_64/kernel/init_task.c:17: warning: implicit declaration of function `__RWSEM_INITIALIZER'
arch/x86_64/kernel/init_task.c:17: warning: missing braces around initializer
arch/x86_64/kernel/init_task.c:17: warning: (near initialization for `init_mm.mmap_sem')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.mmap_sem.activity')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.mmap_sem')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.page_table_lock')
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.mmlist')
...
arch/x86_64/kernel/init_task.c:17: error: initializer element is not constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for `init_mm.default_kioctx')
make[1]: *** [arch/x86_64/kernel/init_task.o] Error 1
make: *** [arch/x86_64/kernel] Error 2


Last edited by pwe on Mon May 16, 2005 6:19 pm; edited 1 time in total
Back to top
View user's profile Send private message
NiLuJe
Guru
Guru


Joined: 06 Nov 2004
Posts: 303
Location: Paris, France

PostPosted: Mon May 16, 2005 6:13 pm    Post subject: Reply with quote

Same error as in the -rc3 with the madwifi drivers :

Code:

# Normal Output
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413)

# Error!
wlan: Unknown symbol __raw_rwlock_is_locked

# Wich leads to:
ath_rate_amrr: Unknown symbol ether_sprintf
ath_rate_amrr: Unknown symbol ieee80211_iterate_nodes
ath_pci: Unknown symbol ieee80211_ioctl_siwrate
ath_pci: Unknown symbol ath_rate_tx_complete
ath_pci: Unknown symbol ieee80211_encap
ath_pci: Unknown symbol ieee80211_input
ath_pci: Unknown symbol ieee80211_ioctl_siwap
ath_pci: Unknown symbol ieee80211_ifattach
ath_pci: Unknown symbol ieee80211_sysctl_register
ath_pci: Unknown symbol ieee80211_ioctl_siwencode
ath_pci: Unknown symbol ieee80211_beacon_update
ath_pci: Unknown symbol ieee80211_ioctl_setmlme
ath_pci: Unknown symbol ieee80211_ioctl_setoptie
ath_pci: Unknown symbol ieee80211_ioctl_giwmode
ath_pci: Unknown symbol ath_rate_attach
ath_pci: Unknown symbol ether_sprintf
ath_pci: Unknown symbol ieee80211_ifdetach
ath_pci: Unknown symbol ieee80211_free_node
ath_pci: Unknown symbol ieee80211_ioctl_siwsens
ath_pci: Unknown symbol ath_rate_newassoc
ath_pci: Unknown symbol ieee80211_notify_michael_failure
ath_pci: Unknown symbol ieee80211_ioctl_chanlist
ath_pci: Unknown symbol ieee80211_ioctl_getparam
ath_pci: Unknown symbol ieee80211_dump_pkt
ath_pci: Unknown symbol ieee80211_ioctl_giwrate
ath_pci: Unknown symbol ieee80211_ioctl_siwrts
ath_pci: Unknown symbol ieee80211_ioctl_giwname
ath_pci: Unknown symbol ath_rate_node_copy
ath_pci: Unknown symbol ieee80211_ioctl_setparam
ath_pci: Unknown symbol ieee80211_ioctl_siwpower
ath_pci: Unknown symbol ieee80211_ioctl_giwsens
ath_pci: Unknown symbol ieee80211_media_change
ath_pci: Unknown symbol ieee80211_ioctl_giwfreq
ath_pci: Unknown symbol ieee80211_beacon_alloc
ath_pci: Unknown symbol ieee80211_ioctl_siwfrag
ath_pci: Unknown symbol ieee80211_ioctl_giwap
ath_pci: Unknown symbol ieee80211_ioctl_siwfreq
ath_pci: Unknown symbol ieee80211_ioctl_giwpower
ath_pci: Unknown symbol ieee80211_find_node
ath_pci: Unknown symbol ieee80211_mhz2ieee
ath_pci: Unknown symbol ieee80211_ioctl_giwrange
ath_pci: Unknown symbol ieee80211_ioctl_giwretry
ath_pci: Unknown symbol ieee80211_ioctl_giwnickn
ath_pci: Unknown symbol ieee80211_ioctl_giwrts
ath_pci: Unknown symbol ieee80211_iw_getstats
ath_pci: Unknown symbol ieee80211_ioctl_addmac
ath_pci: Unknown symbol ath_rate_node_cleanup
ath_pci: Unknown symbol ath_rate_detach
ath_pci: Unknown symbol ieee80211_ioctl_giwfrag
ath_pci: Unknown symbol ieee80211_ioctl_giwencode
ath_pci: Unknown symbol ieee80211_next_scan
ath_pci: Unknown symbol ieee80211_media_init
ath_pci: Unknown symbol ieee80211_ioctl_iwsetup
ath_pci: Unknown symbol ieee80211_ioctl
ath_pci: Unknown symbol ieee80211_ioctl_delmac
ath_pci: Unknown symbol ieee80211_media_status
ath_pci: Unknown symbol ieee80211_announce
ath_pci: Unknown symbol ieee80211_ioctl_setkey
ath_pci: Unknown symbol ieee80211_ioctl_iwaplist
ath_pci: Unknown symbol ieee80211_ioctl_delkey
ath_pci: Unknown symbol ieee80211_ioctl_siwtxpow
ath_pci: Unknown symbol ieee80211_chan2ieee
ath_pci: Unknown symbol ieee80211_ioctl_siwretry
ath_pci: Unknown symbol ieee80211_ioctl_siwnickn
ath_pci: Unknown symbol ieee80211_state_name
ath_pci: Unknown symbol ath_rate_node_init
ath_pci: Unknown symbol ieee80211_ioctl_siwscan
ath_pci: Unknown symbol ieee80211_ioctl_siwmode
ath_pci: Unknown symbol ieee80211_ioctl_getoptie
ath_pci: Unknown symbol ath_rate_findrate
ath_pci: Unknown symbol ieee80211_ioctl_giwessid
ath_pci: Unknown symbol ieee80211_ioctl_giwscan
ath_pci: Unknown symbol ieee80211_crypto_encap
ath_pci: Unknown symbol ieee80211_ioctl_siwessid
ath_pci: Unknown symbol ieee80211_chan2mode
ath_pci: Unknown symbol ieee80211_getrssi
ath_pci: Unknown symbol ath_rate_newstate
ath_pci: Unknown symbol ath_rate_setupxtxdesc
ath_pci: Unknown symbol ieee80211_ioctl_giwtxpow


A quick google search leads me to the RT patchs ... (Madwifi works fine with a vanilla rc4)

Can't test this patchset further because I don't have anymore a wired network :/
Back to top
View user's profile Send private message
fallow
Bodhisattva
Bodhisattva


Joined: 08 Jan 2004
Posts: 2206
Location: Poland

PostPosted: Mon May 16, 2005 6:36 pm    Post subject: Reply with quote

vipernicus wrote:
fallow,
one of your patches is causing me trouble, don't know which one. while in a custom patchset of my own: 2.6.12-rc4-ck1, ext3 -mm fixes, new cfq-ts, I moved 20 gigs of data from one hard drive /multimedia to another on /home/user/multi-backup. Took quite a while, but no problems. Installed your new patchset. changed /multimedia from reiser3.6 to ext3 with full journalling, and set them to move back. went to work, and came back from lunch to find that I had a fatal IO error, it looked like my /home or / had been unmounted. i had to reboot into my own custom ck, and have set the files to move, and have had no problems so far.


what exactly is TEXT describing the problem.
this repeating itself again and again with love and not with other kernels ?

pwe wrote:
anyone compiled this patchset for amd64? i started few minutes ago and after 10sec it fails. ????

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 ;)


will be good If we have an x86_64 maintainer

NiLuJe wrote:
Same error as in the -rc3 with the madwifi drivers :

Code:

# Error!
wlan: Unknown symbol __raw_rwlock_is_locked


A quick google search leads me to the RT patchs ... (Madwifi works fine with a vanilla rc4)

Can't test this patchset further because I don't have anymore a wired network :/


yes this is surely RTP reason . We are not supporting all exotic ( exotic for us , a driver not in vanilla ) drivers , so I think You must find solution yourself , try another patchset just or ask on #love-sources.
Im not sure if job spent on fixing it is worth of it. Maybe easier is just use another kernel :)

cheers & greetings
_________________
"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
View user's profile Send private message
pwe
Guru
Guru


Joined: 12 Mar 2005
Posts: 445
Location: Polska aka Poland

PostPosted: Mon May 16, 2005 6:54 pm    Post subject: Reply with quote

fallow wrote:


pwe wrote:
anyone compiled this patchset for amd64? i started few minutes ago and after 10sec it fails. ????

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 ;)


will be good If we have an x86_64 maintainer


I saw this, You show me this, but ... :wink:
I can test this patchset on my gentoo anytime You WANT :)
Back to top
View user's profile Send private message
vipernicus
Veteran
Veteran


Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.

PostPosted: Mon May 16, 2005 6:57 pm    Post subject: Reply with quote

fallow wrote:
vipernicus wrote:
fallow,
one of your patches is causing me trouble, don't know which one. while in a custom patchset of my own: 2.6.12-rc4-ck1, ext3 -mm fixes, new cfq-ts, I moved 20 gigs of data from one hard drive /multimedia to another on /home/user/multi-backup. Took quite a while, but no problems. Installed your new patchset. changed /multimedia from reiser3.6 to ext3 with full journalling, and set them to move back. went to work, and came back from lunch to find that I had a fatal IO error, it looked like my /home or / had been unmounted. i had to reboot into my own custom ck, and have set the files to move, and have had no problems so far.


what exactly is TEXT describing the problem.
this repeating itself again and again with love and not with other kernels ?


Well, the text was in Gnome, and it said "fatal I/O Error". My desktop would not respond to mouse-clicks, I did a ctrl+alt+backspace, that killed X. No command prompt. Pressed enter a couple of times to see errors about how there was no filesystem (don't know exact errors). Rebooted into my custom kernel, tried same thing, no problems. I use ext3 for /home, /, and ext2 for /boot, and ext3 /multimedia. /multimedia is another hard drive. I was moving 20 gigs from /home/ to /multimedia/ when this error occured. The day before I used another kernel to move the files form /multi to /home.
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog
Back to top
View user's profile Send private message
fallow
Bodhisattva
Bodhisattva


Joined: 08 Jan 2004
Posts: 2206
Location: Poland

PostPosted: Mon May 16, 2005 7:04 pm    Post subject: Reply with quote

pwe wrote:
fallow wrote:


pwe wrote:
anyone compiled this patchset for amd64? i started few minutes ago and after 10sec it fails. ????

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 ;)


will be good If we have an x86_64 maintainer


I saw this, You show me this, but ... :wink:
I can test this patchset on my gentoo anytime You WANT :)


chaosite did testing of vanilla+RTP only . the same error
so this is RTP fault, not love ( our )
will be good to post this error into LKML also

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
View user's profile Send private message
lucke
n00b
n00b


Joined: 11 May 2005
Posts: 35

PostPosted: Mon May 16, 2005 7:26 pm    Post subject: Reply with quote

After some testing it appeared that those quirks aren't due to the alsa patches. However, checking alsa on other kernels allowed me to discover that ck's staircase is really nice and actually behaves better than O(1)+RTP in at least one situation, i.e. starting Opera ;-)
Back to top
View user's profile Send private message
vipernicus
Veteran
Veteran


Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.

PostPosted: Tue May 17, 2005 6:20 am    Post subject: Reply with quote

fallow,
I am about to publish a kernel to sf.net, could I use your def_iosched_select_menu.diff patch?
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum