Re: [gentoo-user] kernel 2.6.25-r6 oddities; is this kernel really ready for stable?

[Dale]

Sebastian Wiesner wrote:
> Dale <dalek1967@×××××××××.net> at Wednesday 23 July 2008, 19:09:45
>
>> Kevin O'Gorman wrote:
>>
>>> I run gentoo x86 stable, so that I usually avoid this sort of thing.
>>>
>>> This kernel, however, looks balky to me, because it's reporting
>>> warnings and other oddities during compilation.  I don't like warnings
>>> at any time, and with the kernel's make wrappers cleaning up the
>>> output they tend to stand out.
>>>
>>> Here's what I get:
>>> -- various type/attribute warnings
>>> -- reports of deprecated elements
>>> -- a report of "section mismatches", and instructions to use "make
>>> CONFIG_DEBUG_SECTION_MISMATCH=y" to find details.
>>>
>>> All that being said, the compilation completes, and I can boot it.  I
>>> don't know the cause, but I have been unable to get vmware-server
>>> running on it, and I'm going back to the previous kernel for that
>>> reason.
>>> << SNIP >>
>>>
>> You are not alone if having "issues" with this kernel.  When I tried to
>> run it recently, I noticed a serious slow down in KDE, especially when
>> logging into KDE.  My usual login time is about 7 to 8 seconds but with
>> this kernel, try about 30 seconds.  My mouse was "jerky" and even
>> Seamonkey was very slow to switch tabs.  Nothing changed but the
>> kernel.  I didn't test to long because it was so annoying.
>>
>
> Don't forget to mention, that sun darkened and rain was coming, once you had
> booted 2.6.25 ...
>
> Compile issues are one thing, but putting all these "application issus" on
> the kernel seems a bit unfair, especially, when admitting, that "you didn't
> test long".
>
> I have seen my KDE login or tab switching in firefox delayed, too, but not
> because of any kernel upgrade, but because "updatedb" was taking action
> right when I was logging in, or because a forgotton compile process on TTY1
> took CPU power away.
>
> I for my part didn't have any problems with 2.6.25-r6, neither at compile
> time nor at runtime
>

Well, I have tested it a few times, recently because of the DVD problem 
with udf, and each time I run that kernel it is slow as syrup on the 
north pole.  Since my updatedb runs in the morning, I'm sure it was not 
running.  I *think* it is something different in how the CPU is done.  I 
show very little hard drive activity when it is logging me into KDE.  
Same with Seamonkey being slow.

It is funny that they are predicting severe thunderstorms and wind here 
today.  Guess that just confirms it.  LOL

Dale

:-)  :-)