Something really nasty happened to my LVM2 with this kernel, and reverting to an older does not help.

From what I can see is that vgscan, lvscan, pvscan and all other lvm2 tools consume 100% CPU ad infinite. I tried recompiling LVM2, remaking the kernel and all other unholy things. Tough I have a cold and is slightly dizzy so somebody should confirm my findings.

Morning chaps,
I've just tried love 2.6.3 rc2 love2 due to the fact I have a new laptop and I wanted to boost my radeon mobility 7500 performance, problem is I'm not getting more than 550fps. I've searched around added the BusID line to XF86Config and everything....

I have the DRM as a module and also have the radeonFB in the kernel

I know something is up as there is no speed difference between running on battery at 600Mhz and plugged in at 1.5GHz

The odd thing is I have had momentary jumps to 700+fps

but nowhere near the 1000+ I should be getting

But everything "looks" ok i the various log files

EDIT

OK dropped depth to 16bpp and now I get around 1250fps

Grrrrr

Is the card just that slow in 24bit mode??

Last edited by deviljelly on Fri Feb 13, 2004 8:51 pm; edited 1 time in total

Personally, I just leave them as they are. I am open to suggestions on how to make the kernel faster (load, run, etc...). As a maintainer, though, I'd like to keep the defaults. It will cause less problems in the end. If we did lots of testing on each potential cflag for stability, then I would be open to suggestions. Love-sources is difficult enough to make stable for each user, adding the cflags would make it that much more dificult. I would like to hear what you have in mind though._________________Rationality is the recognition of the fact that nothing can alter the truth and nothing can take precedence over that act of perceiving it.

I've been working on a patch that makes a couple menuconfig entries that allow you to append CFLAGS to what's generated by your processor selections. I started cleaning it up so it warns the user of how it's generally a silly idea to change CFLAGS, and right now I'm dropping in some printk()s so oopses will (should) say that the kernel was built with hacked CFLAGS.

It's pretty much a personal thing (I like to mess around [1]), but I thought maybe you might be interested.

[1] It's made very little performance difference from what I can tell, although I haven't benchmarked. It's mainly just me goofing around with the kernel and gcc. On that note I've tacked a lot on and have been stable so far on my Athlon XP. Inflated the kernel by about 600 KB too. ;)_________________Website - All sorts of nonsense (some of it actually Linux related)

If it's a menu option, then yeah I'd love to take a look at it. That way we can throw up a fat disclaimer that says "If you use modified CFLAGS while compiling the kernel and experience issues and then blame us, we will come to your house and stab you in the eye with a soldering iron." Email me the patch: jpcox at iastate dot edu_________________Rationality is the recognition of the fact that nothing can alter the truth and nothing can take precedence over that act of perceiving it.

If it's a menu option, then yeah I'd love to take a look at it. That way we can throw up a fat disclaimer that says "If you use modified CFLAGS while compiling the kernel and experience issues and then blame us, we will come to your house and stab you in the eye with a soldering iron." Email me the patch: jpcox at iastate dot edu

We can take their pizza too!

I'll email once I've finished putting the obvious printks in and have given it one last test run._________________Website - All sorts of nonsense (some of it actually Linux related)

It started like this I compiled the new 2.6.3-rc2-love2 kernel and when booting it complained that it could not mount my lvm mounts. I tested booting the old kernel 2.6.2-rc1-love1 and that went fine, then I figured "I probably have to re-emerge the lvm2 stuff" so I booted the new kernel re-emerged lvm2 and device-mapper, and then rebooted to find that it would lock at the "starting LVM" point with any of the kernels.

It took me some playing with the live cd to un-merge lvm2 so that my regular install would boot.

I have after booting, checking kernel settings to my best knowledge and re-merging lvm2 and device-mapper found that issuing any lvm related command causes 100% CPU until i ctrl-c it.

If you would like any configs or anything just ask.

This is not the thing I wished for today being slightly ill and all, when i just tried to type emerge it turned out "wmwefw" and it took me serveral times reading the line before i discovered what had went wrong.

@Peacefaker
I'm not overlooking you, I just don't have a solution to your problem. I don't use lvm2 so I really have no idea what the problem could be._________________Rationality is the recognition of the fact that nothing can alter the truth and nothing can take precedence over that act of perceiving it.

@Steel300
I'm not in anyway saying that don't do a great job, and I know that one man can't know everything. I was just throwing my question out there in hope that someone else might have a similar situation just to make sure I'm not going insane or something.

Ok, so now we have two people both apologising for the fact that their posts might have appeared negative to eachother. Feel the love.

Last edited by Peacefaker on Fri Feb 13, 2004 9:41 pm; edited 1 time in total

@Steel300
I'm not in anyway saying that don't do a great job, and I know that one man can't know everything. I was just throwing my question out there in hope that someone else might have a similar situation just to make sure I'm not going insane or something.

I'm not saying that you are blaming me. I just wanted to let you know that I did hear you question and that you aren't being ignored._________________Rationality is the recognition of the fact that nothing can alter the truth and nothing can take precedence over that act of perceiving it.

I dunno whats going on but it seems that ANY kernel past 2.6.1 hangs at the:

* Bringing eth0 up

shell script... No caps lock response, no Ctrl-Alt-Del response, nada, hard locked. If anyone else running into things like this? A bit frustrating now being able to run the latest kernels.

Gentoo-Dev-Sources 2.6.1 seem to work OK for me but nothing higher. Tried the 2.6.2 and 2.6.3 ones in dev-sources as well as mm-sources of various types. I'm starting to think I'm cursed by an old 2.4 kernel that doesn't want me to leave... ;-P

Is there some basic setting somewhere that would cause this problem?

(eth0 is an onboard intel gigabit, MB is Gigabyte 8KNXP)

[various testing things done]

OK, I finally just mv'd /etc/runlevels/default /etc/runlevels/d and rebooted and it started. So, something in there is hanging me up (Odd) Network driver is compiled into the kernel so I'm going to pick everything apart a bit more.

Just tried /etc/init.d/net.eth0 start and it's frozen now. So it's something related to the Intel Gigabit ethernet driver it seems.. Thats stinky.. Well, I guess I can grab another NIC or something and test some more...hmm

Recompiled the kernel with e1000 as a module, I insmod'd it and blamo, hard lockup. I tihnk it's time to check the kernel mailing lists etc to see if something is FUBAR with e1000 support.

I'm having strange problems/hangs with 2.6.3-rc2-love2 on
a 3 GHz P4 HT (SMP enabled) with ICH5R SATA disks on libata.
These problems have been around for a couple of recent -love
kernel, although some older -love kernels in the 2.6.2-rc* range
were working fine. Plain Linus BK 2.6.3-rc2 + reiser4 works fine, too.
I'm not sure if this is related to SATA, but that could be possible.

Symptom: The system boots OK, but when using it, processes seem to hang
every now and then. xosview seems to indicate the one of the 2 HT
(logical) CPUs sometimes hangs at 100%. Even when doing almost nothing,
load average climbs to above 1. hdparm -t gives erratic performance reports
for the disks - sometimes 55 Mb/s, sometimes 250 Kb/s (Yes, that's
KILObyte). A simple find /usr > /dev/null produces the following "top"
output:

has anyone been able to merge the Win4Lin patches into -mm or -love
trees? I have tried, but without much luck. They seem to collide with
the 4g4g stuff in -mm, as far as I can tell. That's really a pity!

BTW, I'm also looking for User Mode Linux SKAS host patches for
recent 2.6 kernels, but I guess that's even more esoteric....

First Thank You!
This is a Fantastic release!
I see u removed elv-select.patch
The reasons are most justified(although I have been able to use a digital camera just fine).
(Just a thought was everyone using the noop 4 their camera?)
Anyway, I've just been setting the default as cfq and haven't looked back.
Thanks Again,
Baldy

Edit:
Forgot the reason was that in the notes elv-select.patch is mentioned.
Also what's the chances of getting the pwc module included?
I'm getting back this webcam soon and would like to try it out.

I have no idea other than LVM works after I booted the liveCD and rebuild it from there, however now when I boot I have plenty of:
"WARNING: /etc/modprobe.devfs line 22: ignoring bad line starting with 'setenv'

I have a LVM setup (using LVM2 but my volumes are still in lvm-1.5 metadata format) but haven't yet had the time to install and test this new love-source. Will try later this day. (I have backups handy in case...

I have no idea other than LVM works after I booted the liveCD and rebuild it from there, however now when I boot I have plenty of:
"WARNING: /etc/modprobe.devfs line 22: ignoring bad line starting with 'setenv'

Ive just booted the new kernel, and my box crashed, so i hard-rebooted it and then i got some errors with modprobe.conf.

i regenerated it with

Code:

modules-update force

@Steel300

I cant get kernel 2.6.3 and newer to work, it just crash at boot or after some time.
i use the cfq elevator if you need that information

is there any big changes in the new kernel that i should be aware of ?

by the way: the love-sources-2.6.2-r1 works fine. running it now._________________Encrypt, lock up everything and duct tape the rest

I cant get kernel 2.6.3 and newer to work, it just crash at boot or after some time.
i use the cfq elevator if you need that information

is there any big changes in the new kernel that i should be aware of ?

by the way: the love-sources-2.6.2-r1 works fine. running it now.

We really need more information than that - like what does it output just before crashing and is there any trace info to parse to the developers.

I'm really sorry, but Steel300 and the rest of the devs do not read minds.... yet. If you report a bug please include as much information as you can - simply "this crashes" doesn't cut it, it doesn't help us and in return it doesn't help you.

*just a precaution*
and don't ask for supermount nor why we are not in Portage._________________Proud to be a 22 year old Infidel, GNOME lover and member of LIK.