[gentoo-amd64] kwin is crashy

[gentoo-amd64] kwin is crashy

[Volker Armin Hemmann]

Hi,

I have a big kwin problem:
alsmost everytime, when the kwallet password prompt pops up, kwin crashes.

A ram error should not be the culprit - I successfully compiled for hours 
without segfaults and memtest86+ run for some time without errors.

my CFLAGS look like this:
CFLAGS="-march=k8 -O2 -fweb -ftracer -fpeel-loops -msse3 -pipe"

I am pretty annoyed by this (enlightenment does not crash).

The only affected applications are kwin and kicker of kde 3.4.2
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: kwin is crashy

[Duncan]

Volker Armin Hemmann posted
<200509251336.46490.volker.armin.hemmann@tu-clausthal.de>, excerpted
below,  on Sun, 25 Sep 2005 13:36:46 +0200:

> Hi,
> 
> I have a big kwin problem:
> alsmost everytime, when the kwallet password prompt pops up, kwin crashes.
> 
> A ram error should not be the culprit - I successfully compiled for hours 
> without segfaults and memtest86+ run for some time without errors.
> 
> my CFLAGS look like this:
> CFLAGS="-march=k8 -O2 -fweb -ftracer -fpeel-loops -msse3 -pipe"
> 
> I am pretty annoyed by this (enlightenment does not crash).
> 
> The only affected applications are kwin and kicker of kde 3.4.2

Are you sure your CPU handles SSE3?  All except for the newest k8s do not.
SSE2, yes, SSE3, not until the newer ones.  (Confirm that SSE3 appears in
/proc/cpuinfo.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: kwin is crashy

[Volker Armin Hemmann]

On Sunday 25 September 2005 16:36, Duncan wrote:
> Volker Armin Hemmann posted
> <200509251336.46490.volker.armin.hemmann@tu-clausthal.de>, excerpted
>
> below,  on Sun, 25 Sep 2005 13:36:46 +0200:
> > Hi,
> >
> > I have a big kwin problem:
> > alsmost everytime, when the kwallet password prompt pops up, kwin
> > crashes.
> >
> > A ram error should not be the culprit - I successfully compiled for hours
> > without segfaults and memtest86+ run for some time without errors.
> >
> > my CFLAGS look like this:
> > CFLAGS="-march=k8 -O2 -fweb -ftracer -fpeel-loops -msse3 -pipe"
> >
> > I am pretty annoyed by this (enlightenment does not crash).
> >
> > The only affected applications are kwin and kicker of kde 3.4.2
>
> Are you sure your CPU handles SSE3?  All except for the newest k8s do not.
> SSE2, yes, SSE3, not until the newer ones.  (Confirm that SSE3 appears in
> /proc/cpuinfo.)
>

from the OPN it is an E6 venice - and from all the info I found, the Venice 
are the ones with SSE 3

cat /proc/cpuinfo says:
id       : AuthenticAMD
cpu family      : 15
model           : 47
model name      : AMD Athlon(tm) 64 Processor 3200+
stepping        : 2
cpu MHz         : 1000.044
cache size      : 512 KB
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm 
3dnowext 3dnow pni lahf_lm
bogomips        : 2002.31
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc

and pni=sse3 from all I know and read, right?
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: kwin is crashy

[Sebastian Redl]

Volker Armin Hemmann wrote:

>On Sunday 25 September 2005 16:36, Duncan wrote:
>  
>
>from the OPN it is an E6 venice - and from all the info I found, the Venice 
>are the ones with SSE 3
>  
>
cpuinfo is known to return bogus pni support for Athlon64s. More 
information and a program to test for real sse3 support can be found here:
http://www.ussg.iu.edu/hypermail/linux/kernel/0504.3/1027.html

Sebastian Redl
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: kwin is crashy

[Volker Armin Hemmann]

Hi,

On Sunday 25 September 2005 17:35, Sebastian Redl wrote:
> Volker Armin Hemmann wrote:
> >On Sunday 25 September 2005 16:36, Duncan wrote:
> >
> >
> >from the OPN it is an E6 venice - and from all the info I found, the
> > Venice are the ones with SSE 3
>
> cpuinfo is known to return bogus pni support for Athlon64s. More
> information and a program to test for real sse3 support can be found here:
> http://www.ussg.iu.edu/hypermail/linux/kernel/0504.3/1027.html
>
> Sebastian Redl

./test_pni
cpuid(0) returns 1 (AuthenticAMD)
cpuid(1) returns 00020ff2 00000800 00000001 078bfbff
Result is 496498219533200


looks like cpuinfo is correct for me.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: kwin is crashy

[Sebastian Redl]

Volker Armin Hemmann wrote:

>./test_pni
>cpuid(0) returns 1 (AuthenticAMD)
>cpuid(1) returns 00020ff2 00000800 00000001 078bfbff
>Result is 496498219533200
>
>
>looks like cpuinfo is correct for me.
>  
>
In that case, your only choice to find failing CFLAGS is probably to 
remove them selectively.

Sebastian
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: kwin is crashy

[Volker Armin Hemmann]

On Sunday 25 September 2005 18:37, Sebastian Redl wrote:
> Volker Armin Hemmann wrote:
> >./test_pni
> >cpuid(0) returns 1 (AuthenticAMD)
> >cpuid(1) returns 00020ff2 00000800 00000001 078bfbff
> >Result is 496498219533200
> >
> >
> >looks like cpuinfo is correct for me.
>
> In that case, your only choice to find failing CFLAGS is probably to
> remove them selectively.
>
> Sebastian

why do you thing, that it is the CFLAGS 'failing'?
The CPU has sse, says cpuinfo, says test_pni, and the OPN says that it is an 
E6 stepping - which has sse3.

kwin - crash on a picture:
kwin: X_CreatePixmap(0x120096e): BadAlloc (insufficient resources for 
operation)
kwin: X_PolyFillRectangle(0x120096e): BadDrawable (invalid Pixmap or Window 
parameter)
kwin: X_GetImage(0x120096e): BadDrawable (invalid Pixmap or Window parameter)
In file kernel/qpixmap_x11.cpp, line 630: Out of memory
KCrash: Application 'kwin' crashing...

on restart:

kwin
QPixmap: Invalid pixmap parameters
QPainter::begin: Cannot paint null pixmap
QPainter::setFont: Will be reset by begin()
QPainter::setPen: Will be reset by begin()
KCrash: Application 'kwin' crashing...

another crash:
kwin
kwin: X_CreatePixmap(0x1211b7a): BadAlloc (insufficient resources for 
operation)
kwin: X_PolyFillRectangle(0x1211b7a): BadDrawable (invalid Pixmap or Window 
parameter)
kwin: X_GetImage(0x1211b7a): BadDrawable (invalid Pixmap or Window parameter)
In file kernel/qpixmap_x11.cpp, line 630: Out of memory
KCrash: Application 'kwin' crashing...

is what I get, when kwin runs from a konsole.

The 'out of memory' os puzzling, because - well - gkrellm and free are telling 
me, that from my 512 mb ram are more than 150 free, and from my 1gig of swap 
nothing is used.

But I will try and see, what happens, if I recompile QT with guaranteed 
harmless flags.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: kwin is crashy

[Simon Strandman]

Volker Armin Hemmann skrev:

>On Sunday 25 September 2005 18:37, Sebastian Redl wrote:
>  
>
>
>why do you thing, that it is the CFLAGS 'failing'?
>The CPU has sse, says cpuinfo, says test_pni, and the OPN says that it is an 
>E6 stepping - which has sse3.
>
>kwin - crash on a picture:
>kwin: X_CreatePixmap(0x120096e): BadAlloc (insufficient resources for 
>operation)
>kwin: X_PolyFillRectangle(0x120096e): BadDrawable (invalid Pixmap or Window 
>parameter)
>kwin: X_GetImage(0x120096e): BadDrawable (invalid Pixmap or Window parameter)
>In file kernel/qpixmap_x11.cpp, line 630: Out of memory
>KCrash: Application 'kwin' crashing...
>
>on restart:
>
>kwin
>QPixmap: Invalid pixmap parameters
>QPainter::begin: Cannot paint null pixmap
>QPainter::setFont: Will be reset by begin()
>QPainter::setPen: Will be reset by begin()
>KCrash: Application 'kwin' crashing...
>
>another crash:
>kwin
>kwin: X_CreatePixmap(0x1211b7a): BadAlloc (insufficient resources for 
>operation)
>kwin: X_PolyFillRectangle(0x1211b7a): BadDrawable (invalid Pixmap or Window 
>parameter)
>kwin: X_GetImage(0x1211b7a): BadDrawable (invalid Pixmap or Window parameter)
>In file kernel/qpixmap_x11.cpp, line 630: Out of memory
>KCrash: Application 'kwin' crashing...
>
>is what I get, when kwin runs from a konsole.
>
>The 'out of memory' os puzzling, because - well - gkrellm and free are telling 
>me, that from my 512 mb ram are more than 150 free, and from my 1gig of swap 
>nothing is used.
>
>But I will try and see, what happens, if I recompile QT with guaranteed 
>harmless flags.
>  
>

It's a problem with X, here is the bugreport:
https://bugs.freedesktop.org/show_bug.cgi?id=474

-- 
Simon Strandman <simon.strandman@telia.com>

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: kwin is crashy

[Volker Armin Hemmann]

On Sunday 25 September 2005 22:38, Simon Strandman wrote:
> Volker Armin Hemmann skrev:
> >On Sunday 25 September 2005 18:37, Sebastian Redl wrote:
> >
> >
> >
> >why do you thing, that it is the CFLAGS 'failing'?
> >The CPU has sse, says cpuinfo, says test_pni, and the OPN says that it is
> > an E6 stepping - which has sse3.
> >
> >kwin - crash on a picture:
> >kwin: X_CreatePixmap(0x120096e): BadAlloc (insufficient resources for
> >operation)
> >kwin: X_PolyFillRectangle(0x120096e): BadDrawable (invalid Pixmap or
> > Window parameter)
> >kwin: X_GetImage(0x120096e): BadDrawable (invalid Pixmap or Window
> > parameter) In file kernel/qpixmap_x11.cpp, line 630: Out of memory
> >KCrash: Application 'kwin' crashing...
> >
> >on restart:
> >
> >kwin
> >QPixmap: Invalid pixmap parameters
> >QPainter::begin: Cannot paint null pixmap
> >QPainter::setFont: Will be reset by begin()
> >QPainter::setPen: Will be reset by begin()
> >KCrash: Application 'kwin' crashing...
> >
> >another crash:
> >kwin
> >kwin: X_CreatePixmap(0x1211b7a): BadAlloc (insufficient resources for
> >operation)
> >kwin: X_PolyFillRectangle(0x1211b7a): BadDrawable (invalid Pixmap or
> > Window parameter)
> >kwin: X_GetImage(0x1211b7a): BadDrawable (invalid Pixmap or Window
> > parameter) In file kernel/qpixmap_x11.cpp, line 630: Out of memory
> >KCrash: Application 'kwin' crashing...
> >
> >is what I get, when kwin runs from a konsole.
> >
> >The 'out of memory' os puzzling, because - well - gkrellm and free are
> > telling me, that from my 512 mb ram are more than 150 free, and from my
> > 1gig of swap nothing is used.
> >
> >But I will try and see, what happens, if I recompile QT with guaranteed
> >harmless flags.
>
> It's a problem with X, here is the bugreport:
> https://bugs.freedesktop.org/show_bug.cgi?id=474
>
> --
> Simon Strandman <simon.strandman@telia.com>

maybe I am stupid - but this bug was related to mplayer/xine/xv which don't 
have any problems?

But I try the workaround mentioned there, thank you.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: kwin is crashy

[Sebastian Redl]

Volker Armin Hemmann wrote:

>why do you thing, that it is the CFLAGS 'failing'?
>  
>
I don't think that. I just mentioned that it's the only way to find out if.

Sebastian
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: kwin is crashy

[Volker Armin Hemmann]

On Sunday 25 September 2005 22:38, Simon Strandman wrote:

>
> It's a problem with X, here is the bugreport:
> https://bugs.freedesktop.org/show_bug.cgi?id=474

I am pretty sure, that it is not that bug.

The bug is XV related - but I do not have mplayer/xine crashes. Kwin crashes.
Kwin does not crash because of an open xine window, it crashes, when kdewallet 
wants the password.

It is completly independent from openend pictures
It is about ATI cards&drivers (I have nvidia)
The workaround option is ignored in my case.

At least enlightenment works fine.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: kwin is crashy - solved

[Hemmann, Volker Armin]

Hi,

I removed the .kde* files/directories left from my earlier athlon-xp 
installation and everything is fine now.

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: Re: kwin is crashy - solved

[Duncan]

Hemmann, Volker Armin posted
<200509280230.14358.volker.armin.hemmann@tu-clausthal.de>, excerpted
below,  on Wed, 28 Sep 2005 02:30:13 +0200:

> Hi,
> 
> I removed the .kde* files/directories left from my earlier athlon-xp 
> installation and everything is fine now.f

Thanks for reporting your fix.

Of course, people like me get a bit frustrated with such reports, because
we want to know /what/ /file/ caused the problem (we customize our KDE to
the point where removing the entire customization, as this does, would be
unthinkable), and once narrowed down to the file, preferably /what/ /line/
in the file caused the issue.  I'm always copying the config to a backup,
then removing half of it to see if the problem still exists, then either
putting that back and removing the other half, or removing half of what
remains... etc, until I reduce the problem to a single file and usually a
single line within the file, when I suspect my config may be the issue. 
Of course, not everyone has the patience to do such things, but when the
alternative is possibly days recustomizing things, as it can be for
someone with a heavily customized config, a few minutes or hours
spent isolating the problem to a single line in a single file is really
the /easy/ way out!  =8^)

In any case, however, getting the feedback that the problem was solved,
and that it was a config issue, is far more helpful than not ever knowing
/what/ the problem was, so thanks for the fix report!

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: Re: kwin is crashy - solved

[Hemmann, Volker Armin]

On Wednesday 28 September 2005 18:52, Duncan wrote:
> Hemmann, Volker Armin posted
> <200509280230.14358.volker.armin.hemmann@tu-clausthal.de>, excerpted
>
> below,  on Wed, 28 Sep 2005 02:30:13 +0200:
> > Hi,
> >
> > I removed the .kde* files/directories left from my earlier athlon-xp
> > installation and everything is fine now.f
>
> Thanks for reporting your fix.
>
> Of course, people like me get a bit frustrated with such reports, because
> we want to know /what/ /file/ caused the problem (we customize our KDE to
> the point where removing the entire customization, as this does, would be
> unthinkable), and once narrowed down to the file, preferably /what/ /line/
> in the file caused the issue.  I'm always copying the config to a backup,
> then removing half of it to see if the problem still exists, then either
> putting that back and removing the other half, or removing half of what
> remains... etc, until I reduce the problem to a single file and usually a
> single line within the file, when I suspect my config may be the issue.
> Of course, not everyone has the patience to do such things, but when the
> alternative is possibly days recustomizing things, as it can be for
> someone with a heavily customized config, a few minutes or hours
> spent isolating the problem to a single line in a single file is really
> the /easy/ way out!  =8^)

hm, yes, maybe I should have gone the hard way - but I was pretty 
frustrated ;)

And I copied back my konqueror/kmail/kwallet related files - so this ones are 
not the culprits ;)

So, I lost not too much customization - just some colours, the window 
decorations and font-settings...

Maybe it was the fact, that I used baghira with my old installation, which I 
did not installed again.

Glück Auf
Volker

-- 
gentoo-amd64@gentoo.org mailing list