[gentoo-user] KDE and HARD lock ups.

[gentoo-user] KDE and HARD lock ups.

[Dale]

Hi,

Has anyone else had any hard lock ups in KDE?   I'm on kde 4.6.4 which 
was released about a month ago.  For those not in the know, I'm on amd64 
and use kde-meta so it is has the kitchen sink installed here.

What mine does:  It sort of varies but usually when I login, it may last 
a couple minutes, usually less, then the Caps Lock and Scroll Lock LED's 
blink.  The Num Lock key is off if that means anything.  I tried the 
SysReq keys but it doesn't do anything at all.  According to the 
messages at the next boot, it doesn't sync or umount either.  The mouse 
pointer no longer moves either.  At this point, I hit the reset button 
which causes steam to come out my ears.  I HATE using that button.

I'm fairly sure this is not hardware.  Right now, I am in Fluxbox and it 
works fine.  I also booted to single user and compiled a bunch of stuff 
and also tried a different kernel too.  I think if it was hardware, it 
would have had some kind of hick-up during the compile.  I did check 
temps and all is nice and cool, very cool since my A/C is on full 
blast.  I think the oven is outside on full blast instead of in the 
kitchen.  lol  It's HOT here, steamy hot.

I checked messages and the only thing I saw was about a bad option for 
hp-systray.  Surely that wouldn't cause a crash?  I'm going to unmerge 
and test it tho, just to be sure.

Anyone run into something like this?  Ideas?

Thanks much.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Jesús J. Guerrero Botella]

2011/7/4 Dale <rdalek1967@gmail.com>:
> Hi,
>
> What mine does:  It sort of varies but usually when I login, it may last a
> couple minutes, usually less, then the Caps Lock and Scroll Lock LED's
> blink.  The Num Lock key is off if that means anything.  I tried the SysReq
> keys but it doesn't do anything at all.  According to the messages at the
> next boot, it doesn't sync or umount either.  The mouse pointer no longer
> moves either.  At this point, I hit the reset button which causes steam to
> come out my ears.  I HATE using that button.
>
> I'm fairly sure this is not hardware.

You can never be sure about that.

>  Right now, I am in Fluxbox and it
> works fine.  I also booted to single user and compiled a bunch of stuff and
> also tried a different kernel too.  I think if it was hardware, it would
> have had some kind of hick-up during the compile.  I did check temps and all
> is nice and cool, very cool since my A/C is on full blast.  I think the oven
> is outside on full blast instead of in the kitchen.  lol  It's HOT here,
> steamy hot.

You can try turning off the compositing system altogether. You can do
that by disabling the desktop effects in systemsettings. If lockups
stop then it's probably something to do with your graphics driver and
if that's the case you might have better luck with an alternative
driver.

> I checked messages and the only thing I saw was about a bad option for
> hp-systray.  Surely that wouldn't cause a crash?  I'm going to unmerge and
> test it tho, just to be sure.

I don't think so.


-- 
Jesús Guerrero Botella

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Jesús J. Guerrero Botella wrote:
> 2011/7/4 Dale<rdalek1967@gmail.com>:
>    
>> Hi,
>>
>> What mine does:  It sort of varies but usually when I login, it may last a
>> couple minutes, usually less, then the Caps Lock and Scroll Lock LED's
>> blink.  The Num Lock key is off if that means anything.  I tried the SysReq
>> keys but it doesn't do anything at all.  According to the messages at the
>> next boot, it doesn't sync or umount either.  The mouse pointer no longer
>> moves either.  At this point, I hit the reset button which causes steam to
>> come out my ears.  I HATE using that button.
>>
>> I'm fairly sure this is not hardware.
>>      
> You can never be sure about that.
>    

That's why I said "fairly".  One can never be sure but after some 
testing, I don't think it is hardware.  I'm getting more sure of that as 
time goes on too.  ;-)

>    
>>   Right now, I am in Fluxbox and it
>> works fine.  I also booted to single user and compiled a bunch of stuff and
>> also tried a different kernel too.  I think if it was hardware, it would
>> have had some kind of hick-up during the compile.  I did check temps and all
>> is nice and cool, very cool since my A/C is on full blast.  I think the oven
>> is outside on full blast instead of in the kitchen.  lol  It's HOT here,
>> steamy hot.
>>      
> You can try turning off the compositing system altogether. You can do
> that by disabling the desktop effects in systemsettings. If lockups
> stop then it's probably something to do with your graphics driver and
> if that's the case you might have better luck with an alternative
> driver.
>
>    

I don't think I am logged in long enough to change the settings.  I may 
try my test user but I think a file got corrupted or something.  I did 
have a power failure the other day and the relay on my UPS was not quite 
fast enough.  I think the contacts may need some cleaning.  My UPS does 
some odd things at times.  I need a new one but they are pricey.  I had 
forgot about the power failure issue.  That has lead me down a different 
path now.

>> I checked messages and the only thing I saw was about a bad option for
>> hp-systray.  Surely that wouldn't cause a crash?  I'm going to unmerge and
>> test it tho, just to be sure.
>>      
> I don't think so.
>
>    

I have seen this cause my desktop to freeze before.  Usually when it has 
trouble seeing the printer or starting itself then kills itself after a 
few seconds.  Once it dies, the desktop comes back.  This is just a more 
permanent freeze.  I did wait a couple times but it never come back.

Working on a re-emerge to see if it corrects this issue.

Thanks.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Alan McKinnon]

On Monday 04 July 2011 19:12:50 Jesús J. Guerrero Botella did opine 
thusly:
> 2011/7/4 Dale <rdalek1967@gmail.com>:
> > Hi,
> > 
> > What mine does:  It sort of varies but usually when I login, it
> > may last a couple minutes, usually less, then the Caps Lock and
> > Scroll Lock LED's blink.  The Num Lock key is off if that means
> > anything.  I tried the SysReq keys but it doesn't do anything
> > at all.  According to the messages at the next boot, it doesn't
> > sync or umount either.  The mouse pointer no longer moves
> > either.  At this point, I hit the reset button which causes
> > steam to come out my ears.  I HATE using that button.
> > 
> > I'm fairly sure this is not hardware.
> 
> You can never be sure about that.
> 
> >  Right now, I am in Fluxbox and it
> > works fine.  I also booted to single user and compiled a bunch
> > of stuff and also tried a different kernel too.  I think if it
> > was hardware, it would have had some kind of hick-up during the
> > compile.  I did check temps and all is nice and cool, very cool
> > since my A/C is on full blast.  I think the oven is outside on
> > full blast instead of in the kitchen.  lol  It's HOT here,
> > steamy hot.
> 
> You can try turning off the compositing system altogether. You can
> do that by disabling the desktop effects in systemsettings. If
> lockups stop then it's probably something to do with your graphics
> driver and if that's the case you might have better luck with an
> alternative driver.

I get frequent crashes that seem to be related to nouveau.
When I used nvidia drivers, they seemed to have a mind of their own 
when it came to memory usage and segfaults.
And the entire abomination that shall not be suffered to live called 
"kdepim" *definitely* has a mind of it's own.


> 
> > I checked messages and the only thing I saw was about a bad
> > option for hp-systray.  Surely that wouldn't cause a crash?
> >  I'm going to unmerge and test it tho, just to be sure.
> 
> I don't think so.
-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] KDE and HARD lock ups.

[Volker Armin Hemmann]

On Monday 04 July 2011 11:48:51 Dale wrote:
> Hi,
> Has anyone else had any hard lock ups in KDE?   I'm on kde 4.6.4 whichwas 
released about a month ago.  For those not in the know, I'm on amd64and use 
kde-meta so it is has the kitchen sink installed here.
> What mine does:  It sort of varies but usually when I login, it may lasta 
couple minutes, usually less, then the Caps Lock and Scroll Lock LED'sblink.  
The Num Lock key is off if that means anything.  I tried theSysReq keys but it 
doesn't do anything at all.  According to themessages at the next boot, it 
doesn't sync or umount either.  The mousepointer no longer moves either.  At 
this point, I hit the reset buttonwhich causes steam to come out my ears.  I 
HATE using that button.
> I'm fairly sure this is not hardware.  Right now, I am in Fluxbox and 
itworks fine.  I also booted to single user and compiled a bunch of stuffand 
also tried a different kernel too.  I think if it was hardware, itwould have 
had some kind of hick-up during the compile.  I did checktemps and all is nice 
and cool, very cool since my A/C is on fullblast.  I think the oven is outside 
on full blast instead of in thekitchen.  lol  It's HOT here, steamy hot.
> I checked messages and the only thing I saw was about a bad option forhp-
systray.  Surely that wouldn't cause a crash?  I'm going to unmergeand test it 
tho, just to be sure.
> Anyone run into something like this?  Ideas?
> Thanks much.
> Dale
> :-)  :-)

I only had lockups thanks to USB which haven't occured since I switched to 
2.6.39.2

-- 
#163933

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Alan McKinnon wrote:
> On Monday 04 July 2011 19:12:50 Jesús J. Guerrero Botella did opine
> thusly:
>    
>> 2011/7/4 Dale<rdalek1967@gmail.com>:
>>      
>>> Hi,
>>>
>>> What mine does:  It sort of varies but usually when I login, it
>>> may last a couple minutes, usually less, then the Caps Lock and
>>> Scroll Lock LED's blink.  The Num Lock key is off if that means
>>> anything.  I tried the SysReq keys but it doesn't do anything
>>> at all.  According to the messages at the next boot, it doesn't
>>> sync or umount either.  The mouse pointer no longer moves
>>> either.  At this point, I hit the reset button which causes
>>> steam to come out my ears.  I HATE using that button.
>>>
>>> I'm fairly sure this is not hardware.
>>>        
>> You can never be sure about that.
>>
>>      
>>>   Right now, I am in Fluxbox and it
>>> works fine.  I also booted to single user and compiled a bunch
>>> of stuff and also tried a different kernel too.  I think if it
>>> was hardware, it would have had some kind of hick-up during the
>>> compile.  I did check temps and all is nice and cool, very cool
>>> since my A/C is on full blast.  I think the oven is outside on
>>> full blast instead of in the kitchen.  lol  It's HOT here,
>>> steamy hot.
>>>        
>> You can try turning off the compositing system altogether. You can
>> do that by disabling the desktop effects in systemsettings. If
>> lockups stop then it's probably something to do with your graphics
>> driver and if that's the case you might have better luck with an
>> alternative driver.
>>      
> I get frequent crashes that seem to be related to nouveau.
> When I used nvidia drivers, they seemed to have a mind of their own
> when it came to memory usage and segfaults.
> And the entire abomination that shall not be suffered to live called
> "kdepim" *definitely* has a mind of it's own.
>
>
>    
>>      
>>> I checked messages and the only thing I saw was about a bad
>>> option for hp-systray.  Surely that wouldn't cause a crash?
>>>   I'm going to unmerge and test it tho, just to be sure.
>>>        
>> I don't think so.
>>      

Well, I tried a different kernel.  Same thing.  I tried reseting the 
BIOS and lurking around in there for a bit as well.  Same thing.  So, 
right now I'm chewing on a emerge -e kde-meta.  After I remembered the 
power failure the other day, I suspect a corrupt file somewhere.  I'm 
just glad I have Fluxbox on here.  I'm in it right now and it works OK.  
I just wish the little bar at the bottom was larger.  So far, nothing I 
click changes that.  Tough on my eyes too.  Teeny tiny stuff down 
there.  o_o

Thinking back, I should have booted the CD and run file system checks.  
Crap, the one thing I didn't think of. < sighs >

I still use Nvidia's driver here.  it has worked well for me at least.  
I don't use any fancy hardware or play any serious games so it works 
well, so far at least.  That may change next week.  lol   You know me.  
Something new pretty regular.

I don't guess I use kdepim stuff.  It's installed so who knows.  Any 
relation to pam?

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Jesús J. Guerrero Botella]

2011/7/4 Dale <rdalek1967@gmail.com>:
> I don't think I am logged in long enough to change the settings.  I may try
> my test user but I think a file got corrupted or something.  I did have a
> power failure the other day and the relay on my UPS was not quite fast
> enough.  I think the contacts may need some cleaning.  My UPS does some odd
> things at times.  I need a new one but they are pricey.  I had forgot about
> the power failure issue.  That has lead me down a different path now.

You don't need much time. The default shortcut to disable compositing
in kde is shift+alt+f12

You can try the vesa driver, or any alternative that will work with
your card, as well.

I also had the usb issue that others said above, with previous kernel
versions. I haven't seen it lately though, with 2.6.39.x.

-- 
Jesús Guerrero Botella

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Jesús J. Guerrero Botella wrote:
> 2011/7/4 Dale<rdalek1967@gmail.com>:
>    
>> I don't think I am logged in long enough to change the settings.  I may try
>> my test user but I think a file got corrupted or something.  I did have a
>> power failure the other day and the relay on my UPS was not quite fast
>> enough.  I think the contacts may need some cleaning.  My UPS does some odd
>> things at times.  I need a new one but they are pricey.  I had forgot about
>> the power failure issue.  That has lead me down a different path now.
>>      
> You don't need much time. The default shortcut to disable compositing
> in kde is shift+alt+f12
>
> You can try the vesa driver, or any alternative that will work with
> your card, as well.
>
> I also had the usb issue that others said above, with previous kernel
> versions. I haven't seen it lately though, with 2.6.39.x.
>
>    

I may try that if this re-emerge doesn't help any.  It doesn't like 
much.  I just hope all the thunder I keep hearing will not force me to 
shutdown my rig.  I think Mother Nature is hungry since the tummy is 
growling a lot.  :/

Hmmm, I use Nvidia for my drivers.  I don't even know if vesa is on here 
or not.  I might add that Fluxbox has been working.  It even plays 
videos fine.  I'm not sure this is a video driver problem, not yet anyway.

I been using 2.6.38 for a while.  I seem to have missed the USB bug.  I 
don't have much that uses it except for my printer and my camera.  I 
don't even have my printer hooked up most of them time.  Maybe I do have 
some good luck after all.  o_O

Thanks.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Gregory Shearman]

Jesús J. Guerrero Botella <jesus.guerrero.botella@gmail.com>  wrote:
> 2011/7/4 Dale <rdalek1967@gmail.com>:
>> I don't think I am logged in long enough to change the settings.  I may try
>> my test user but I think a file got corrupted or something.  I did have a
>> power failure the other day and the relay on my UPS was not quite fast
>> enough.  I think the contacts may need some cleaning.  My UPS does some odd
>> things at times.  I need a new one but they are pricey.  I had forgot about
>> the power failure issue.  That has lead me down a different path now.
>
> You don't need much time. The default shortcut to disable compositing
> in kde is shift+alt+f12
>

You can also edit the user KDE config directly via:

~/.kde4/share/config/kwinrc

[Compositing]

Enabled=True

change to

Enabled=False

There's more than one way to skin a cat.

-- 
Regards,
Gregory.

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Gregory Shearman wrote:
> Jesús J. Guerrero Botella<jesus.guerrero.botella@gmail.com>   wrote:
>    
>> 2011/7/4 Dale<rdalek1967@gmail.com>:
>>      
>>> I don't think I am logged in long enough to change the settings.  I may try
>>> my test user but I think a file got corrupted or something.  I did have a
>>> power failure the other day and the relay on my UPS was not quite fast
>>> enough.  I think the contacts may need some cleaning.  My UPS does some odd
>>> things at times.  I need a new one but they are pricey.  I had forgot about
>>> the power failure issue.  That has lead me down a different path now.
>>>        
>> You don't need much time. The default shortcut to disable compositing
>> in kde is shift+alt+f12
>>
>>      
> You can also edit the user KDE config directly via:
>
> ~/.kde4/share/config/kwinrc
>
> [Compositing]
>
> Enabled=True
>
> change to
>
> Enabled=False
>
> There's more than one way to skin a cat.
>
>    

Ahhh, I figured there was a config file somewhere but wasn't sure what 
it would be called.  Now I know how to do it with nano.  lol

Thanks much for the pointer.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Jesús J. Guerrero Botella]

2011/7/5 Dale <rdalek1967@gmail.com>:
> Jesús J. Guerrero Botella wrote:
>>
>> 2011/7/4 Dale<rdalek1967@gmail.com>:
>>
>>>
>>> I don't think I am logged in long enough to change the settings.  I may
>>> try
>>> my test user but I think a file got corrupted or something.  I did have a
>>> power failure the other day and the relay on my UPS was not quite fast
>>> enough.  I think the contacts may need some cleaning.  My UPS does some
>>> odd
>>> things at times.  I need a new one but they are pricey.  I had forgot
>>> about
>>> the power failure issue.  That has lead me down a different path now.
>>>
>>
>> You don't need much time. The default shortcut to disable compositing
>> in kde is shift+alt+f12
>>
>> You can try the vesa driver, or any alternative that will work with
>> your card, as well.
>>
>> I also had the usb issue that others said above, with previous kernel
>> versions. I haven't seen it lately though, with 2.6.39.x.
>>
>>
>
> I may try that if this re-emerge doesn't help any.  It doesn't like much.  I
> just hope all the thunder I keep hearing will not force me to shutdown my
> rig.  I think Mother Nature is hungry since the tummy is growling a lot.  :/
>
> Hmmm, I use Nvidia for my drivers.  I don't even know if vesa is on here or
> not.  I might add that Fluxbox has been working.  It even plays videos fine.
>  I'm not sure this is a video driver problem, not yet anyway.

There's one very important difference and it relates to all the post
I've written in this thread: compositing. Fluxbox doesn't use that.

You will need to start trying something sooner or later, if you
discard problems like that without any further looking you might not
find the problem ever.

> I been using 2.6.38 for a while.  I seem to have missed the USB bug.  I
> don't have much that uses it except for my printer and my camera.  I don't
> even have my printer hooked up most of them time.  Maybe I do have some good
> luck after all.  o_O

A lot of people were hit by a nasty bug that hard locked the pc when
plugging in usb storage devices. Your camera would fit that category.
I remember a thread in the forum where most users affected by this had
a similar motherboard and chipset.

http://forums.gentoo.org/viewtopic-t-882390-highlight-.html

There's been some noise about this in many places, not just that
thread. So you might want to take a look at it if you can't solve your
problem recompiling the tray app.



-- 
Jesús Guerrero Botella

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Jesús J. Guerrero Botella wrote:
> 2011/7/5 Dale<rdalek1967@gmail.com>:
>    
>> Jesús J. Guerrero Botella wrote:
>>      
>>> 2011/7/4 Dale<rdalek1967@gmail.com>:
>>>
>>>        
>>>> I don't think I am logged in long enough to change the settings.  I may
>>>> try
>>>> my test user but I think a file got corrupted or something.  I did have a
>>>> power failure the other day and the relay on my UPS was not quite fast
>>>> enough.  I think the contacts may need some cleaning.  My UPS does some
>>>> odd
>>>> things at times.  I need a new one but they are pricey.  I had forgot
>>>> about
>>>> the power failure issue.  That has lead me down a different path now.
>>>>
>>>>          
>>> You don't need much time. The default shortcut to disable compositing
>>> in kde is shift+alt+f12
>>>
>>> You can try the vesa driver, or any alternative that will work with
>>> your card, as well.
>>>
>>> I also had the usb issue that others said above, with previous kernel
>>> versions. I haven't seen it lately though, with 2.6.39.x.
>>>
>>>
>>>        
>> I may try that if this re-emerge doesn't help any.  It doesn't like much.  I
>> just hope all the thunder I keep hearing will not force me to shutdown my
>> rig.  I think Mother Nature is hungry since the tummy is growling a lot.  :/
>>
>> Hmmm, I use Nvidia for my drivers.  I don't even know if vesa is on here or
>> not.  I might add that Fluxbox has been working.  It even plays videos fine.
>>   I'm not sure this is a video driver problem, not yet anyway.
>>      
> There's one very important difference and it relates to all the post
> I've written in this thread: compositing. Fluxbox doesn't use that.
>
> You will need to start trying something sooner or later, if you
> discard problems like that without any further looking you might not
> find the problem ever.
>
>    

I tried it.  It still did the same thing.  It did make things look 
different tho.  Sort of made it look funny in a way.  That would be 
funny as in strange.


>> I been using 2.6.38 for a while.  I seem to have missed the USB bug.  I
>> don't have much that uses it except for my printer and my camera.  I don't
>> even have my printer hooked up most of them time.  Maybe I do have some good
>> luck after all.  o_O
>>      
> A lot of people were hit by a nasty bug that hard locked the pc when
> plugging in usb storage devices. Your camera would fit that category.
> I remember a thread in the forum where most users affected by this had
> a similar motherboard and chipset.
>
> http://forums.gentoo.org/viewtopic-t-882390-highlight-.html
>
> There's been some noise about this in many places, not just that
> thread. So you might want to take a look at it if you can't solve your
> problem recompiling the tray app.
>
>    

I may have found the problem.  It appears openldap has a issue which 
effects some KDE packages as well.  Started a fresh thread for that one.

Thanks.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Dale wrote:
>
> Well, I tried a different kernel.  Same thing.  I tried reseting the 
> BIOS and lurking around in there for a bit as well.  Same thing.  So, 
> right now I'm chewing on a emerge -e kde-meta.  After I remembered the 
> power failure the other day, I suspect a corrupt file somewhere.  I'm 
> just glad I have Fluxbox on here.  I'm in it right now and it works 
> OK.  I just wish the little bar at the bottom was larger.  So far, 
> nothing I click changes that.  Tough on my eyes too.  Teeny tiny stuff 
> down there.  o_o
>
> Thinking back, I should have booted the CD and run file system 
> checks.  Crap, the one thing I didn't think of. < sighs >
>
> I still use Nvidia's driver here.  it has worked well for me at 
> least.  I don't use any fancy hardware or play any serious games so it 
> works well, so far at least.  That may change next week.  lol   You 
> know me.  Something new pretty regular.
>
> I don't guess I use kdepim stuff.  It's installed so who knows.  Any 
> relation to pam?
>
> Dale
>
> :-)  :-)
>

Well, I got rid of openldap.  It runs longer but still crashes so I am 
back to Fluxbox again, which works fine.  I also started with a fresh 
.kde4 directory.  That seemed to help more than anything else.  It 
lasted a LOT longer after that.  I don't know if it was a coincidence or 
what but it did lock up once when I logged into Konsole as root.

I started a emerge -e world this time.  This thing has 4 cores so it 
won't take to long.  Any ideas on what else I can try?  If this emerge 
doesn't help, it has to be a config file somewhere.

Again, I'm pretty sure it is not hardware.  It runs fine when compiling 
in a console and I have run from systemrescue stick as well.  Hardware 
seems to work fine.

Ideas?

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Paul Hartman]

On Tue, Jul 5, 2011 at 2:23 PM, Dale <rdalek1967@gmail.com> wrote:
> Dale wrote:
>>
>> Well, I tried a different kernel.  Same thing.  I tried reseting the BIOS
>> and lurking around in there for a bit as well.  Same thing.  So, right now
>> I'm chewing on a emerge -e kde-meta.  After I remembered the power failure
>> the other day, I suspect a corrupt file somewhere.  I'm just glad I have
>> Fluxbox on here.  I'm in it right now and it works OK.  I just wish the
>> little bar at the bottom was larger.  So far, nothing I click changes that.
>>  Tough on my eyes too.  Teeny tiny stuff down there.  o_o
>>
>> Thinking back, I should have booted the CD and run file system checks.
>>  Crap, the one thing I didn't think of. < sighs >
>>
>> I still use Nvidia's driver here.  it has worked well for me at least.  I
>> don't use any fancy hardware or play any serious games so it works well, so
>> far at least.  That may change next week.  lol   You know me.  Something new
>> pretty regular.
>>
>> I don't guess I use kdepim stuff.  It's installed so who knows.  Any
>> relation to pam?
>>
>> Dale
>>
>> :-)  :-)
>>
>
> Well, I got rid of openldap.  It runs longer but still crashes so I am back
> to Fluxbox again, which works fine.  I also started with a fresh .kde4
> directory.  That seemed to help more than anything else.  It lasted a LOT
> longer after that.  I don't know if it was a coincidence or what but it did
> lock up once when I logged into Konsole as root.
>
> I started a emerge -e world this time.  This thing has 4 cores so it won't
> take to long.  Any ideas on what else I can try?  If this emerge doesn't
> help, it has to be a config file somewhere.
>
> Again, I'm pretty sure it is not hardware.  It runs fine when compiling in a
> console and I have run from systemrescue stick as well.  Hardware seems to
> work fine.
>
> Ideas?

It's a long shot, but since you're using nvidia, I had random lockups.
It turned out to be due to faulty handling of the on-by-default
aggressive power savings mode of my Nvidia card. It was solved by
placing this undocumented incantation, pieced together from various
Google searches, in my xorg.conf device section for my video card:

Section "Device"
    Identifier "nVidia GT 240"
    Driver "nvidia"
    Option "RegistryDWords" "PowerMizerEnable=0x1;
PerfLevelSrc=0x3322; PowerMizerDefault=0x1; PowerMizerDefaultAC=0x1"
EndSection

After that, everything works wonderfully.

You can also use nvidia-settings to change the power saving mode at
run-time, but it does not save it and you must do it every time you
log into X, which is annoying. The xorg.conf method above requires no
further action.

Your card may not even support PowerMizer, who knows? I thought I'd
mention it just in case.

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Paul Hartman wrote:
> On Tue, Jul 5, 2011 at 2:23 PM, Dale<rdalek1967@gmail.com>  wrote:
>    
>>
>> Well, I got rid of openldap.  It runs longer but still crashes so I am back
>> to Fluxbox again, which works fine.  I also started with a fresh .kde4
>> directory.  That seemed to help more than anything else.  It lasted a LOT
>> longer after that.  I don't know if it was a coincidence or what but it did
>> lock up once when I logged into Konsole as root.
>>
>> I started a emerge -e world this time.  This thing has 4 cores so it won't
>> take to long.  Any ideas on what else I can try?  If this emerge doesn't
>> help, it has to be a config file somewhere.
>>
>> Again, I'm pretty sure it is not hardware.  It runs fine when compiling in a
>> console and I have run from systemrescue stick as well.  Hardware seems to
>> work fine.
>>
>> Ideas?
>>      
> It's a long shot, but since you're using nvidia, I had random lockups.
> It turned out to be due to faulty handling of the on-by-default
> aggressive power savings mode of my Nvidia card. It was solved by
> placing this undocumented incantation, pieced together from various
> Google searches, in my xorg.conf device section for my video card:
>
> Section "Device"
>      Identifier "nVidia GT 240"
>      Driver "nvidia"
>      Option "RegistryDWords" "PowerMizerEnable=0x1;
> PerfLevelSrc=0x3322; PowerMizerDefault=0x1; PowerMizerDefaultAC=0x1"
> EndSection
>
> After that, everything works wonderfully.
>
> You can also use nvidia-settings to change the power saving mode at
> run-time, but it does not save it and you must do it every time you
> log into X, which is annoying. The xorg.conf method above requires no
> further action.
>
> Your card may not even support PowerMizer, who knows? I thought I'd
> mention it just in case.
>
>    

I haven't updated the drivers in a while.  Would something like that 
just up and change even with no upgrade?   I ask because I don't 
honestly know the answer.  Also, would it not cause problems in Fluxbox 
as well?  I played video in Fluxbox last night and it never missed a 
beat.  I use smplayer to play videos just like I do in KDE.

This is what sort of confuses me.  KDE was locking up usually in less 
than a minute after logging in.  After getting rid of openldap, it did 
the same.  After renaming my .kde4 directory, it lasted several minutes 
before locking up.  During one lockup, I even got the SysReq key to work 
and could reboot.  The last time was a HARD lock up complete with the 
flashing lights on my keyboard.

If this still locks up after emerge -e world and a reboot, I'm not sure 
what to do next.  That should eliminate a corrupt file.  Renaming .kde4 
fixed KDE config problems so that doesn't leave much.  I'm going to log 
into my test user and see what if anything it does.  I'm not going to do 
any tinkering with settings, just the default stuff.  I'll post back 
later what it does.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Dale wrote:
> Paul Hartman wrote:
>> On Tue, Jul 5, 2011 at 2:23 PM, Dale<rdalek1967@gmail.com>  wrote:
>>>
>>> Well, I got rid of openldap.  It runs longer but still crashes so I 
>>> am back
>>> to Fluxbox again, which works fine.  I also started with a fresh .kde4
>>> directory.  That seemed to help more than anything else.  It lasted 
>>> a LOT
>>> longer after that.  I don't know if it was a coincidence or what but 
>>> it did
>>> lock up once when I logged into Konsole as root.
>>>
>>> I started a emerge -e world this time.  This thing has 4 cores so it 
>>> won't
>>> take to long.  Any ideas on what else I can try?  If this emerge 
>>> doesn't
>>> help, it has to be a config file somewhere.
>>>
>>> Again, I'm pretty sure it is not hardware.  It runs fine when 
>>> compiling in a
>>> console and I have run from systemrescue stick as well.  Hardware 
>>> seems to
>>> work fine.
>>>
>>> Ideas?
>> It's a long shot, but since you're using nvidia, I had random lockups.
>> It turned out to be due to faulty handling of the on-by-default
>> aggressive power savings mode of my Nvidia card. It was solved by
>> placing this undocumented incantation, pieced together from various
>> Google searches, in my xorg.conf device section for my video card:
>>
>> Section "Device"
>>      Identifier "nVidia GT 240"
>>      Driver "nvidia"
>>      Option "RegistryDWords" "PowerMizerEnable=0x1;
>> PerfLevelSrc=0x3322; PowerMizerDefault=0x1; PowerMizerDefaultAC=0x1"
>> EndSection
>>
>> After that, everything works wonderfully.
>>
>> You can also use nvidia-settings to change the power saving mode at
>> run-time, but it does not save it and you must do it every time you
>> log into X, which is annoying. The xorg.conf method above requires no
>> further action.
>>
>> Your card may not even support PowerMizer, who knows? I thought I'd
>> mention it just in case.
>>
>
> I haven't updated the drivers in a while.  Would something like that 
> just up and change even with no upgrade?   I ask because I don't 
> honestly know the answer.  Also, would it not cause problems in 
> Fluxbox as well?  I played video in Fluxbox last night and it never 
> missed a beat.  I use smplayer to play videos just like I do in KDE.
>
> This is what sort of confuses me.  KDE was locking up usually in less 
> than a minute after logging in.  After getting rid of openldap, it did 
> the same.  After renaming my .kde4 directory, it lasted several 
> minutes before locking up.  During one lockup, I even got the SysReq 
> key to work and could reboot.  The last time was a HARD lock up 
> complete with the flashing lights on my keyboard.
>
> If this still locks up after emerge -e world and a reboot, I'm not 
> sure what to do next.  That should eliminate a corrupt file.  Renaming 
> .kde4 fixed KDE config problems so that doesn't leave much.  I'm going 
> to log into my test user and see what if anything it does.  I'm not 
> going to do any tinkering with settings, just the default stuff.  I'll 
> post back later what it does.
>
> Dale
>
> :-)  :-)
>

I added the line to my xorg file.  Just in case.  ;-)

I logged into my test user with a clean .kde4 directory.  It took a few 
minutes but it did lock up when I opened Konsole again.  I booted my USB 
stick again and did a check on the file systems.  It says everything is 
fine but I'm doing a fresh install on my spare drive.  It was a drive 
that I got along with my video card.  Anyway, I'm going to test the new 
drive here in a little while and see if it still locks up or what.  I 
copied over some files in /etc and my world file plus distfiles.  I'm 
trying not to copy over any more than I have to.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 430 bytes --]

On Tue, 5 Jul 2011 15:07:44 -0500, Paul Hartman wrote:

> You can also use nvidia-settings to change the power saving mode at
> run-time, but it does not save it and you must do it every time you
> log into X, which is annoying.

Can't you put nvidia-settings -l in xinitrc or autostart?

That's the official way of loading the settings at login.


-- 
Neil Bothwick

I wouldn't be caught dead with a necrophiliac.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] KDE and HARD lock ups.

[Jesús J. Guerrero Botella]

Dale, random hard-lockups are only due to hardware or kerne, it can't
be otherwisel (drivers count as part of kernel). The fact that
compilation doesn't lock your system only means that the thing
(whatever it is) is not bount to intensive I/O operations and/or high
cpu loads.

Openldap itself can't hard lock up anything if the kernel doesn't give
it permissions to do so (kernel bug) or if the hardware is not faulty.
Same goes for tray apps.

-- 
Jesús Guerrero Botella

Re: [gentoo-user] KDE and HARD lock ups.

[Jesús J. Guerrero Botella]

Just to discard some basic things, you could run a SMART check in your
disks and memtest86+ in your RAM. The fact that a memory intensive
desktop locks the computer that flux didn't might mean a thing there
(or not).

-- 
Jesús Guerrero Botella

Re: [gentoo-user] KDE and HARD lock ups.

[Paul Hartman]

On Tue, Jul 5, 2011 at 6:04 PM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Tue, 5 Jul 2011 15:07:44 -0500, Paul Hartman wrote:
>
>> You can also use nvidia-settings to change the power saving mode at
>> run-time, but it does not save it and you must do it every time you
>> log into X, which is annoying.
>
> Can't you put nvidia-settings -l in xinitrc or autostart?
>
> That's the official way of loading the settings at login.

If I remember, this option could not be set by commandline, only by
the nvidia-settings GUI. Maybe it has been added since then.

Re: [gentoo-user] KDE and HARD lock ups.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 868 bytes --]

On Tue, 5 Jul 2011 18:14:52 -0500, Paul Hartman wrote:

> > Can't you put nvidia-settings -l in xinitrc or autostart?
> >
> > That's the official way of loading the settings at login.  
> 
> If I remember, this option could not be set by commandline, only by
> the nvidia-settings GUI. Maybe it has been added since then.

When you quit the GUI, the settings are supposed to be saved to
~/.nvidia-settings-rc and loaded from there when you load the GUI. The -l
switch tells nvidia-settings to load the settings from that file and
quit, so it should do what you need.

The settings file is plain text, so it's easy to see whether the setting
you want is saved there, it may even be possible to add it manually,
although that rather defeats the object of a GUI.


-- 
Neil Bothwick

Eye of newt, toe of frog, regular Coke and fries to go, please.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Jesús J. Guerrero Botella wrote:
> Dale, random hard-lockups are only due to hardware or kerne, it can't
> be otherwisel (drivers count as part of kernel). The fact that
> compilation doesn't lock your system only means that the thing
> (whatever it is) is not bount to intensive I/O operations and/or high
> cpu loads.
>
> Openldap itself can't hard lock up anything if the kernel doesn't give
> it permissions to do so (kernel bug) or if the hardware is not faulty.
> Same goes for tray apps.
>
>    

I might add, the last time it locked up, I had a compile process running 
in a console.  I watched the hard drive light, it was blinking away.  
So, the root of the system was running but for some reason, I could not 
get my mouse or keyboard to work.  It appears it is the GUI part that is 
locking up but whatever it is, it is not affecting Fluxbox.  I also 
tried the shift alt F12 to disable composite as well.

It also ran from the my USB stick which is systemrescue.  I didn't start 
a GUI tho.  I just used it to run file system checks and such.

Does that make any sense?  It's not making any here.  I'm just trying to 
nail Jello to the wall.  lol

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Volker Armin Hemmann]

On Tuesday 05 July 2011 15:41:13 Dale wrote:

update your fucking drivers.

Seriously, no userspace app does something like this. The driver is broken, 
KDE touches the broken part and BOOM.

Don't blame KDE, blame nvidia.

And update the driver.


-- 
#163933

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]

Volker Armin Hemmann wrote:
> On Tuesday 05 July 2011 15:41:13 Dale wrote:
>
> update your fucking drivers.
>
> Seriously, no userspace app does something like this. The driver is broken,
> KDE touches the broken part and BOOM.
>
> Don't blame KDE, blame nvidia.
>
> And update the driver.
>
>
>    

I don't think a bad video driver would cause this:

*root@fireball / # emerge -av =x11-drivers/nvidia-drivers-270.41.19

These are the packages that would be merged, in order:

Calculating dependencies |

!!! Invalid or corrupt dependency specification:

Invalid atom (????1), token 1

(dev-perl/Net-SSLeay-1.36::unxlngx, installed)

Portage is unable to process the dependencies of the 'dev-perl/Net-
SSLeay-1.36' package. In order to correct this problem, the package
should be uninstalled, reinstalled, or upgraded. As a temporary
workaround, the --nodeps option can be used to ignore all dependencies.
For reference, the problematic dependencies can be found in the *DEPEND
files located in '/var/db/pkg/dev-perl/Net-SSLeay-1.36/'.
... done!
root@fireball / #

Whatever the problems is, things are breaking.  I think something in KDE 
is broke, like corrupt file or some corrupt config somewhere, and it was 
just the first symptom of the problem.  No matter what I try to emerge, 
I get errors like this.

Still think emerging a new video driver is going to help?  ;-)

Dale

:-)  :-)
*

[-- Attachment #2: Type: text/html, Size: 1889 bytes --]

Re: [gentoo-user] KDE and HARD lock ups.

[Paul Hartman]

On Tue, Jul 5, 2011 at 6:49 PM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Tue, 5 Jul 2011 18:14:52 -0500, Paul Hartman wrote:
>
>> > Can't you put nvidia-settings -l in xinitrc or autostart?
>> >
>> > That's the official way of loading the settings at login.
>>
>> If I remember, this option could not be set by commandline, only by
>> the nvidia-settings GUI. Maybe it has been added since then.
>
> When you quit the GUI, the settings are supposed to be saved to
> ~/.nvidia-settings-rc and loaded from there when you load the GUI. The -l
> switch tells nvidia-settings to load the settings from that file and
> quit, so it should do what you need.
>
> The settings file is plain text, so it's easy to see whether the setting
> you want is saved there, it may even be possible to add it manually,
> although that rather defeats the object of a GUI.

Unfortunately those settings are not saved in the file by the GUI, but
if they were it would have been easy as you described. :)

Re: [gentoo-user] KDE and HARD lock ups.

[Paul Hartman]

On Tue, Jul 5, 2011 at 11:16 PM, Dale <rdalek1967@gmail.com> wrote:
>
> Whatever the problems is, things are breaking.  I think something in KDE is
> broke, like corrupt file or some corrupt config somewhere, and it was just
> the first symptom of the problem.  No matter what I try to emerge, I get
> errors like this.

I would definitely run sys-apps/memtest86+ for a few hours (or
more)... Random lockups and corruption sounds like RAM issues.

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Paul Hartman wrote:
> On Tue, Jul 5, 2011 at 11:16 PM, Dale<rdalek1967@gmail.com>  wrote:
>    
>> Whatever the problems is, things are breaking.  I think something in KDE is
>> broke, like corrupt file or some corrupt config somewhere, and it was just
>> the first symptom of the problem.  No matter what I try to emerge, I get
>> errors like this.
>>      
> I would definitely run sys-apps/memtest86+ for a few hours (or
> more)... Random lockups and corruption sounds like RAM issues.
>
>
>    

I had a power failure the other day not long before this started.  
Needless to say, this has the potential of leading to problems with 
files, which is what I thought was wrong with KDE.  I don't KNOW that 
this is the problem but it is a possibility.  After the install gets 
done, I do plan to run some tests before even booting into the new install.

I just hope this drive isn't going out on me.  It's not to old but we 
all know how they are.  They break when they are ready, not when it is 
convenient for us.

If the tests fail, then maybe I can fix some things in my old install 
after some repairs.  If it passes the test, I hope the new install does 
better.  I'll report what happens tho.

Thinking about it, I got 16Gbs on here.  That could take a while to 
test.  O_O

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Paul Hartman]

On Wed, Jul 6, 2011 at 12:12 AM, Dale <rdalek1967@gmail.com> wrote:
> Thinking about it, I got 16Gbs on here.  That could take a while to test.
>  O_O

When I'm in a hurry I just run test 5, it seems that 99% of the time
that's the test that finds errors anyway. Best, of course, is to run
them all, but I usually do test 5 only first since it's more likely to
fail sooner and can do passes faster. :) Then if it does NOT fail I'll
run all tests, just to be sure.

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Paul Hartman wrote:
> On Wed, Jul 6, 2011 at 12:12 AM, Dale<rdalek1967@gmail.com>  wrote:
>    
>> Thinking about it, I got 16Gbs on here.  That could take a while to test.
>>   O_O
>>      
> When I'm in a hurry I just run test 5, it seems that 99% of the time
> that's the test that finds errors anyway. Best, of course, is to run
> them all, but I usually do test 5 only first since it's more likely to
> fail sooner and can do passes faster. :) Then if it does NOT fail I'll
> run all tests, just to be sure.
>
>
>    

I didn't know that.  I'll start with it then let it run at least a 
couple passes of a full test.  I got some good ram so I sort of think it 
is OK.  I really think the power failure the other day messed up 
something, drive itself, some file or something that is causing this.  I 
just get the sense there is a snowball coming tho.

My current plan, finish this new install.  Test the ram and hope it is 
OK.  Test the new install and see if it holds up.  If it does, I plan to 
test the heck out of the old drive.  If it passes tests then I may copy 
my install over and test it again.  If it fails, door stop most likely.  
Are they even worth shipping back anymore?  It may not even be under 
warranty now tho.  It's about a year old.

I'm just hoping for a fix SOON.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Volker Armin Hemmann]

On Tuesday 05 July 2011 23:16:21 Dale wrote:
> Volker Armin Hemmann wrote:
> > On Tuesday 05 July 2011 15:41:13 Dale wrote:> 
> > update your fucking drivers.> 
> > Seriously, no userspace app does something like this. The driver is
> > broken, KDE touches the broken part and BOOM.> 
> > Don't blame KDE, blame nvidia.> 
> > And update the driver.
> I don't think a bad video driver would cause this:
> *root@fireball / # emerge -av =x11-drivers/nvidia-drivers-270.41.19
> These are the packages that would be merged, in order:
> Calculating dependencies |
> !!! Invalid or corrupt dependency specification:
> Invalid atom (????1), token 1
> (dev-perl/Net-SSLeay-1.36::unxlngx, installed)
> Portage is unable to process the dependencies of the 'dev-perl/Net-
SSLeay-1.36' package. In order to correct this problem, the packageshould be 
uninstalled, reinstalled, or upgraded. As a temporaryworkaround, the --nodeps 
option can be used to ignore all dependencies.For reference, the problematic 
dependencies can be found in the *DEPENDfiles located in '/var/db/pkg/dev-
perl/Net-SSLeay-1.36/'.... done!root@fireball / #
> Whatever the problems is, things are breaking.  I think something in KDEis 
broke, like corrupt file or some corrupt config somewhere, and it wasjust the 
first symptom of the problem.  No matter what I try to emerge,I get errors 
like this.
> Still think emerging a new video driver is going to help?  ;-)
> Dale
> :-)  :-)
> *

kde does not corrupt /var/db and does not lock up machines.

Bad video drivers do lock up machines

And machines locking up are prone to damage their file systems.

-- 
#163933

Re: [gentoo-user] KDE and HARD lock ups.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]

On Tue, 5 Jul 2011 23:19:00 -0500, Paul Hartman wrote:

> > When you quit the GUI, the settings are supposed to be saved to
> > ~/.nvidia-settings-rc and loaded from there when you load the GUI.
> > The -l switch tells nvidia-settings to load the settings from that
> > file and quit, so it should do what you need.
> >
> > The settings file is plain text, so it's easy to see whether the
> > setting you want is saved there, it may even be possible to add it
> > manually, although that rather defeats the object of a GUI.  
> 
> Unfortunately those settings are not saved in the file by the GUI, but
> if they were it would have been easy as you described. :)

So the man page should be updated to state "When nvidia-settings exits,
it queries the current settings from the X server and saves SOME OF them
to the configuration file." :(


-- 
Neil Bothwick

Programming Language: (n.) a shorthand way of describing a series of bugs
                      to a computer or a programmer.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Volker Armin Hemmann wrote:
> On Tuesday 05 July 2011 23:16:21 Dale wrote:
>    
>> Volker Armin Hemmann wrote:
>>      
>>> On Tuesday 05 July 2011 15:41:13 Dale wrote:>
>>> update your fucking drivers.>
>>> Seriously, no userspace app does something like this. The driver is
>>> broken, KDE touches the broken part and BOOM.>
>>> Don't blame KDE, blame nvidia.>
>>> And update the driver.
>>>        
>> I don't think a bad video driver would cause this:
>> *root@fireball / # emerge -av =x11-drivers/nvidia-drivers-270.41.19
>> These are the packages that would be merged, in order:
>> Calculating dependencies |
>> !!! Invalid or corrupt dependency specification:
>> Invalid atom (????1), token 1
>> (dev-perl/Net-SSLeay-1.36::unxlngx, installed)
>> Portage is unable to process the dependencies of the 'dev-perl/Net-
>>      
> SSLeay-1.36' package. In order to correct this problem, the packageshould be
> uninstalled, reinstalled, or upgraded. As a temporaryworkaround, the --nodeps
> option can be used to ignore all dependencies.For reference, the problematic
> dependencies can be found in the *DEPENDfiles located in '/var/db/pkg/dev-
> perl/Net-SSLeay-1.36/'.... done!root@fireball / #
>    
>> Whatever the problems is, things are breaking.  I think something in KDEis
>>      
> broke, like corrupt file or some corrupt config somewhere, and it wasjust the
> first symptom of the problem.  No matter what I try to emerge,I get errors
> like this.
>    
>> Still think emerging a new video driver is going to help?  ;-)
>> Dale
>> :-)  :-)
>> *
>>      
> kde does not corrupt /var/db and does not lock up machines.
>
> Bad video drivers do lock up machines
>
> And machines locking up are prone to damage their file systems.
>
>    

But again, it didn't lock up until AFTER I had a power failure.  That 
was when all this started.  If I hadn't had the power failure, I may not 
have had the lock ups to begin with.  The root of this problem is what I 
am hoping to find.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 489 bytes --]

On Wed, 06 Jul 2011 02:27:21 -0500, Dale wrote:

> But again, it didn't lock up until AFTER I had a power failure.  That 
> was when all this started.  If I hadn't had the power failure, I may
> not have had the lock ups to begin with.  The root of this problem is
> what I am hoping to find.

It sounds like you need to start with qcheck -aBT and trawl through the
output, re-emerging anything questionable.


-- 
Neil Bothwick

Every morning is the dawn of a new error...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Neil Bothwick wrote:
> On Wed, 06 Jul 2011 02:27:21 -0500, Dale wrote:
>
>    
>> But again, it didn't lock up until AFTER I had a power failure.  That
>> was when all this started.  If I hadn't had the power failure, I may
>> not have had the lock ups to begin with.  The root of this problem is
>> what I am hoping to find.
>>      
> It sounds like you need to start with qcheck -aBT and trawl through the
> output, re-emerging anything questionable.
>
>
>    
This is what I got:

root@fireball / # qcheck -aBT
app-office/openoffice
sys-auth/consolekit
sys-auth/polkit
net-nds/openldap
app-misc/screen
net-print/cups
net-print/hplip
sys-apps/dbus
sys-apps/openrc
dev-db/mysql
kde-base/kdm
root@fireball / #

That hplip makes me wonder.  I had issues with that thing before causing 
freezes, not lock ups tho.  I should have expected openoffice to be on 
there tho. lol

Hmmm.  What you think about that list?  Anything look suspicious?

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Alan McKinnon]

On Wednesday 06 July 2011 03:52:54 Volker Armin Hemmann did opine 
thusly:
> On Tuesday 05 July 2011 15:41:13 Dale wrote:
> 
> update your fucking drivers.

Upset with nVidia perhaps?

> Seriously, no userspace app does something like this. The driver is
> broken, KDE touches the broken part and BOOM.
> 
> Don't blame KDE, blame nvidia.
> 
> And update the driver.

I had reasonable shit with nvidia drivers, especially the bit where it 
doesn't do 2 screens the way I want.

So I switched to -9999 nouveau and now I have endless shit with 
crashes. But I can tolerate that and not whinge.

I freely admit to being biased.


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Dale wrote:
> Neil Bothwick wrote:
>> On Wed, 06 Jul 2011 02:27:21 -0500, Dale wrote:
>>
>>> But again, it didn't lock up until AFTER I had a power failure.  That
>>> was when all this started.  If I hadn't had the power failure, I may
>>> not have had the lock ups to begin with.  The root of this problem is
>>> what I am hoping to find.
>> It sounds like you need to start with qcheck -aBT and trawl through the
>> output, re-emerging anything questionable.
>>
>>
> This is what I got:
>
> root@fireball / # qcheck -aBT
> app-office/openoffice
> sys-auth/consolekit
> sys-auth/polkit
> net-nds/openldap
> app-misc/screen
> net-print/cups
> net-print/hplip
> sys-apps/dbus
> sys-apps/openrc
> dev-db/mysql
> kde-base/kdm
> root@fireball / #
>
> That hplip makes me wonder.  I had issues with that thing before 
> causing freezes, not lock ups tho.  I should have expected openoffice 
> to be on there tho. lol
>
> Hmmm.  What you think about that list?  Anything look suspicious?
>
> Dale
>
> :-)  :-)
>

OK.  I rebuilt all that . . . stuff plus a few others portage was 
pitching a fit about.  That would exclude openldap.  See one of the 
other threads on what happens when I try to compile that    stuff.   I'm 
getting like Alan here.  I'm tired and my nice shiny puter has a low 
gloss spot.  Grrrr.  Anyway, I can compile again at least.

Let's think here.  polkit, hplip really raises my eyebrows, dbus, mysql 
are things that KDE uses and Fluxbox don't.  I just wonder if one of 
those could be corrupt or something.  I use a slideshow for my 
background.  It usually locks up while setting up that thing.  It scans 
ALL the picture files or something.  I assume it builds some sort of 
data base which may use mysql.  Still giving that hplip the evil eye 
tho.  I know for sure that caused issues in the past.  I have had times 
where I wanted to shoot that little . . . thing.  lol

Still trying to finish the new install.  I my not need it but still.  
After it gets done, going to run memtest and try out that option 5.  I 
dunno either but I'm going to try it.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Urs Schutz]

On Wed, 06 Jul 2011 03:53:23 -0500
Dale <rdalek1967@gmail.com> wrote:

snipped

> >>
> > This is what I got:
> >
> > root@fireball / # qcheck -aBT
> > app-office/openoffice
> > sys-auth/consolekit
> > sys-auth/polkit
> > net-nds/openldap
> > app-misc/screen
> > net-print/cups
> > net-print/hplip
> > sys-apps/dbus
> > sys-apps/openrc
> > dev-db/mysql
> > kde-base/kdm
> > root@fireball / #
> >
> > That hplip makes me wonder.  I had issues with that
> > thing before causing freezes, not lock ups tho.  I
> > should have expected openoffice to be on there tho. lol
> >
> > Hmmm.  What you think about that list?  Anything look
> > suspicious?
> >
> > Dale

Just a hint without further proof:
I had soffice -quickstart (from LibreOffice) running as
panel app, and had kernel crashes. Since I do not start the
LibreOffice quickstarter anymore, i have a stable system
again.
This is with LibreOffice 3.3.2; OOO330m19 (Build:202) and
WMaker wmsystemtray.

Urs 

Re: [gentoo-user] KDE and HARD lock ups.

[Peter Ruskin]

On Wednesday 06 July 2011 08:35:04 Neil Bothwick wrote:
> It sounds like you need to start with qcheck -aBT and trawl
> through the output, re-emerging anything questionable.

I don't think I trust the output of that:

# qcheck -aBT
mail-mta/postfix
app-shells/bash
net-fs/nfs-utils
net-fs/samba
app-text/gtkspell
app-text/gnome-doc-utils
app-text/dictd
net-nntp/pan
x11-misc/lineakd
x11-misc/shared-mime-info
x11-themes/hicolor-icon-theme
x11-themes/baghira
sys-fs/udev
dev-libs/libIDL
dev-libs/rasqal
dev-libs/libusb
dev-libs/atk
app-misc/ca-certificates
app-portage/cfg-update
media-fonts/font-alias
x11-libs/libwnck
x11-libs/libXrender
x11-libs/libXdamage
x11-libs/gtksourceview
gnome-base/libgnome-keyring
gnome-base/gnome-keyring
gnome-extra/libgsf
gnome-extra/polkit-gnome
kde-base/networkstatus
kde-base/arts
kde-base/lisa
kde-base/libkdegames
kde-base/akregator
kde-base/ksim
kde-base/kdesdk-kfile-plugins
kde-base/kdepasswd
kde-base/kmenuedit
kde-base/kdepim-kresources
kde-base/libkcal
kde-base/kpf
kde-base/ktnef
kde-base/kdict
kde-base/libkdepim
kde-base/kaddressbook-plugins
kde-base/kdeartwork-styles
kde-base/libkscan
kde-base/karm
kde-base/kworldclock
kde-base/kdm
kde-base/libkmime
kde-base/librss
kde-base/kicker-applets
kde-base/kdemultimedia-kfile-plugins
kde-base/kdemultimedia-kioslaves
kde-base/libkholidays
kde-base/kdvi
kde-base/kate
kde-base/libkpimexchange
kde-base/kfax
kde-base/khexedit
kde-base/khelpcenter
kde-base/libkdenetwork
kde-base/kxkb
kde-base/kdenetwork-kfile-plugins
kde-base/kdf
kde-base/kdegraphics-kfile-plugins
kde-base/konqueror
kde-base/konsole
kde-base/knewsticker
kde-base/kdeadmin-kfile-plugins
kde-base/krfb
kde-base/kget
kde-base/kedit
kde-base/kode
kde-base/ksmserver
kde-base/kmid
kde-base/kompare
kde-base/kviewshell
kde-base/kweather
kde-base/kdenetwork-filesharing
kde-base/kfind
kde-base/kdesdk-misc
kde-base/kate-plugins
kde-base/kdeartwork-kwin-styles
kde-base/kdemultimedia-arts
kde-base/kghostview
kde-base/kregexpeditor
kde-base/mimelib
kde-base/kfilereplace
kde-base/konq-plugins
kde-base/kcharselect
kde-base/konqueror-akregator
kde-base/kdepim-l10n
kde-base/certmanager
kde-base/kdeaddons-kfile-plugins
kde-base/libkpimidentities
kde-base/renamedlg-images
kde-base/kview
kde-base/kdm
kde-base/kdepim-kioslaves
kde-base/libksieve
kde-base/kontact
kde-base/libkonq
kde-base/quanta
media-video/vcdimager
app-office/libreoffice
media-plugins/kipi-plugins
net-print/cups
net-print/hplip
net-print/gutenprint
sys-apps/dbus
sys-apps/usbutils
sys-apps/pciutils
sys-apps/shadow
sys-apps/openrc
sys-apps/baselayout
net-nds/openldap
sys-libs/gdbm
sys-libs/glibc
sys-devel/gcc
sys-devel/binutils
sys-devel/gcc
net-misc/wget
net-misc/ntp
net-misc/openssh
net-libs/libktorrent
dev-db/mariadb
app-cdr/k3b
app-admin/sudo
app-admin/logrotate
app-admin/webmin
app-admin/sysklogd
app-editors/kxmleditor
app-editors/vim-core
sys-auth/polkit-kde-agent
sys-auth/polkit
sys-auth/consolekit
media-gfx/kuickshow
media-gfx/kphotoalbum
media-sound/vorbis-tools
media-sound/awesfx
media-sound/normalize
media-sound/alsa-utils
dev-games/ggz-client-libs
x11-base/xorg-server
media-libs/libexif
media-libs/alsa-oss
media-libs/liblqr
media-libs/fontconfig
media-libs/t1lib
media-libs/libdvdnav
sys-block/gparted

-- 
Peter
========================================================================
Gentoo Linux: Portage 2.2.0_alpha28		kernel-2.6.38-gentoo-r2
AMD Phenom(tm) 9950 Quad-Core Processor		gcc(Gentoo: 4.5.2)
KDE: 3.5.10					Qt: 3.3.8b
========================================================================

Re: [gentoo-user] KDE and HARD lock ups.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 789 bytes --]

On Wed, 06 Jul 2011 03:08:03 -0500, Dale wrote:

> > It sounds like you need to start with qcheck -aBT and trawl through
> > the output, re-emerging anything questionable.

> This is what I got:
> 
> root@fireball / # qcheck -aBT
> app-office/openoffice
> sys-auth/consolekit
> sys-auth/polkit
> net-nds/openldap
> app-misc/screen
> net-print/cups
> net-print/hplip
> sys-apps/dbus
> sys-apps/openrc
> dev-db/mysql
> kde-base/kdm
> root@fireball / #
> 
You need to check the full output for each package, some of them may be
configuration file changes and re-emerge anything doubtful.

I take it you have done a full fsck and smartctl check of the filesystem
and drive.


-- 
Neil Bothwick

An expert is nothing more than an ordinary person away from home.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] KDE and HARD lock ups.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 509 bytes --]

On Wed, 6 Jul 2011 10:36:40 +0100, Peter Ruskin wrote:

> > It sounds like you need to start with qcheck -aBT and trawl
> > through the output, re-emerging anything questionable.  
> 
> I don't think I trust the output of that:
> 
> # qcheck -aBT
[big snip]

It produces false positives and you need to look at the output for each
affected package, but do you know a better way of detecting corruption
of installed files?


-- 
Neil Bothwick

My brain's in gear, neutral's a gear ain't it?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] KDE and HARD lock ups.

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 754 bytes --]

On Wednesday 06 Jul 2011 10:51:20 Neil Bothwick wrote:
> On Wed, 6 Jul 2011 10:36:40 +0100, Peter Ruskin wrote:
> > > It sounds like you need to start with qcheck -aBT and trawl
> > > through the output, re-emerging anything questionable.
> > 
> > I don't think I trust the output of that:
> > 
> > # qcheck -aBT
> 
> [big snip]
> 
> It produces false positives and you need to look at the output for each
> affected package, but do you know a better way of detecting corruption
> of installed files?

I wasn't familiar with qcheck (yes, I know, I lead a sheltered life!) but 
adding --verbose does not reveal additional info.  When you say "look at the 
output", do you mean the output of emerge -1aDv <package> ?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] KDE and HARD lock ups.

[Tanstaafl]

On 2011-07-06 3:27 AM, Dale wrote:
> But again, it didn't lock up until AFTER I had a power failure. That 
> was when all this started. If I hadn't had the power failure, I may
> not have had the lock ups to begin with. The root of this problem is
> what I am hoping to find.

More than once I have seen power failures damage power supplies, causing
fluctuating voltages that can cause all kinds of weird problems...

I'd try dropping in a new power supply if the memory tests pass, before
giving up...

Re: [gentoo-user] KDE and HARD lock ups.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 824 bytes --]

On Wed, 6 Jul 2011 11:37:54 +0100, Mick wrote:

> > It produces false positives and you need to look at the output for
> > each affected package, but do you know a better way of detecting
> > corruption of installed files?  
> 
> I wasn't familiar with qcheck (yes, I know, I lead a sheltered life!)
> but adding --verbose does not reveal additional info.  When you say
> "look at the output", do you mean the output of emerge -1aDv <package> ?

The -B option restricts the output to just the names of packages with
changed files. If you feed this list back to qcheck with just the -T
option, you'll get a list of affected files.

qcheck -aBT >foo
qcheck -T $(cat foo)

You may want to pipe the output from the second through grep -v /etc/


-- 
Neil Bothwick

Who messed with my anti-paranoia shot?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] KDE and HARD lock ups.

[Peter Humphrey]

On Wednesday 06 July 2011 01:03:03 Dale wrote:

> I might add, the last time it locked up, I had a compile process running
> in a console.  I watched the hard drive light, it was blinking away.
> So, the root of the system was running but for some reason, I could not
> get my mouse or keyboard to work.  It appears it is the GUI part that is
> locking up but whatever it is, it is not affecting Fluxbox.  I also
> tried the shift alt F12 to disable composite as well.

This is sounding more and more like the lockups I've been experiencing. In 
my case it was every distro other than Gentoo.

I'm trying Fedora with "Asus Express Gate" switched off in the BIOS, and it 
seems to be helping. I know you don't have an Asus motherboard though, so 
I'm not helping :-(

When did you last recompile your kernel? What version is it? (Sorry if 
you've told us already, but if so I missed it.)

-- 
Rgds
Peter

Re: [gentoo-user] KDE and HARD lock ups.

[Mark Knecht]

On Wed, Jul 6, 2011 at 7:44 AM, Peter Humphrey <peter@humphrey.ukfsn.org> wrote:
> On Wednesday 06 July 2011 01:03:03 Dale wrote:
>
>> I might add, the last time it locked up, I had a compile process running
>> in a console.  I watched the hard drive light, it was blinking away.
>> So, the root of the system was running but for some reason, I could not
>> get my mouse or keyboard to work.  It appears it is the GUI part that is
>> locking up but whatever it is, it is not affecting Fluxbox.  I also
>> tried the shift alt F12 to disable composite as well.
>
> This is sounding more and more like the lockups I've been experiencing. In
> my case it was every distro other than Gentoo.
>
> I'm trying Fedora with "Asus Express Gate" switched off in the BIOS, and it
> seems to be helping. I know you don't have an Asus motherboard though, so
> I'm not helping :-(
>
> When did you last recompile your kernel? What version is it? (Sorry if
> you've told us already, but if so I missed it.)
>
> --
> Rgds
> Peter

Speaking as someone who runs 100% (except when I don't) I wonder if
this is driven at all by the use of testing packages?

I have only Asus & Intel MB's and laptops here. They all use the
NVidia closed source testing driver except one which uses the Intel
driver. None of them are experiencing any lockups at any time that I
know of.

This is pretty typical of where I don't run stable:

c2stable ~ # cat /etc/portage/package.keywords
sys-kernel/gentoo-sources ~amd64
sys-apps/portage ~*
app-portage/eix ~amd64
app-emulation/virtualbox ~amd64
app-emulation/virtualbox-modules ~amd64
app-emulation/virtualbox-additions ~amd64
x11-drivers/xf86-video-virtualbox ~amd64
x11-drivers/xf86-input-virtualbox ~amd64
app-emulation/vmware-modules ~amd64
app-emulation/vmware-tools ~amd64
app-emulation/vmware-player ~amd64
x11-libs/libview ~amd64
sci-libs/ta-lib ~amd64
sys-power/cpufrequtils ~amd64
media-libs/tiff ~amd64
dev-util/nvidia-cuda-toolkit ~amd64
dev-util/nvidia-cuda-sdk ~amd64
x11-drivers/nvidia-drivers ~amd64
dev-util/codeblocks ~amd64
x11-misc/read-edid ~amd64
net-im/skype ~amd64
app-forensics/chkrootkit ~amd64
dev-lang/R ~amd64
c2stable ~ #

Cheers,
Mark

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Jesús J. Guerrero Botella wrote:
> Dale, random hard-lockups are only due to hardware or kerne, it can't
> be otherwisel (drivers count as part of kernel). The fact that
> compilation doesn't lock your system only means that the thing
> (whatever it is) is not bount to intensive I/O operations and/or high
> cpu loads.
>
> Openldap itself can't hard lock up anything if the kernel doesn't give
> it permissions to do so (kernel bug) or if the hardware is not faulty.
> Same goes for tray apps.
>
>    

OK.  I tested this and it doesn't help any.  I tried three different 
kernels, all of which I have used in the past with no problems, and get 
the same thing.  I have tried reinstalling nvidia-drivers and a 
different versions of nvidia-drivers, same thing.  So, either previously 
working kernels are now broke, nvidia which was working fine just a few 
days ago with no recent updates here just broke or just maybe it is 
something else we have yet to figure out yet.  I also ran memtest for 
HOURS with not one problem reported.

Given I have tried the above, do you still think it is kernel, nvidia or 
hardware?  I'm about to run tests on the drive now.  I suspect it is 
going to show no problems as well.

This is also the reason I keep old kernels laying around:

root@fireball / # ls -al /boot/bzImage*
-rw-r--r-- 1 root root 4257840 Mar 21 18:39 /boot/bzImage-2.6.38-1
-rw-r--r-- 1 root root 4480304 Mar 22 12:00 /boot/bzImage-2.6.38-2
-rw-r--r-- 1 root root 4493872 Mar 25 13:02 /boot/bzImage-2.6.38-3
-rw-r--r-- 1 root root 4496336 Mar 29 03:25 /boot/bzImage-2.6.38-r1-1
-rw-r--r-- 1 root root 4454480 Apr  7 19:13 /boot/bzImage-2.6.38-r1-2
-rw-r--r-- 1 root root 4451760 May  3 02:16 /boot/bzImage-2.6.38-r3-1
-rw-r--r-- 1 root root 4451536 May 12 06:12 /boot/bzImage-2.6.38-r5-1
root@fireball / #

I did try .39 but it had issues.  I got rid of those.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Mark Knecht]

On Wed, Jul 6, 2011 at 12:27 PM, Dale <rdalek1967@gmail.com> wrote:
> Jesús J. Guerrero Botella wrote:
>>
>> Dale, random hard-lockups are only due to hardware or kerne, it can't
>> be otherwisel (drivers count as part of kernel). The fact that
>> compilation doesn't lock your system only means that the thing
>> (whatever it is) is not bount to intensive I/O operations and/or high
>> cpu loads.
>>
>> Openldap itself can't hard lock up anything if the kernel doesn't give
>> it permissions to do so (kernel bug) or if the hardware is not faulty.
>> Same goes for tray apps.
>>
>>
>
> OK.  I tested this and it doesn't help any.  I tried three different
> kernels, all of which I have used in the past with no problems, and get the
> same thing.  I have tried reinstalling nvidia-drivers and a different
> versions of nvidia-drivers, same thing.  So, either previously working
> kernels are now broke, nvidia which was working fine just a few days ago
> with no recent updates here just broke or just maybe it is something else we
> have yet to figure out yet.  I also ran memtest for HOURS with not one
> problem reported.
>
> Given I have tried the above, do you still think it is kernel, nvidia or
> hardware?  I'm about to run tests on the drive now.  I suspect it is going
> to show no problems as well.
>
> This is also the reason I keep old kernels laying around:
>
> root@fireball / # ls -al /boot/bzImage*
> -rw-r--r-- 1 root root 4257840 Mar 21 18:39 /boot/bzImage-2.6.38-1
> -rw-r--r-- 1 root root 4480304 Mar 22 12:00 /boot/bzImage-2.6.38-2
> -rw-r--r-- 1 root root 4493872 Mar 25 13:02 /boot/bzImage-2.6.38-3
> -rw-r--r-- 1 root root 4496336 Mar 29 03:25 /boot/bzImage-2.6.38-r1-1
> -rw-r--r-- 1 root root 4454480 Apr  7 19:13 /boot/bzImage-2.6.38-r1-2
> -rw-r--r-- 1 root root 4451760 May  3 02:16 /boot/bzImage-2.6.38-r3-1
> -rw-r--r-- 1 root root 4451536 May 12 06:12 /boot/bzImage-2.6.38-r5-1
> root@fireball / #
>
> I did try .39 but it had issues.  I got rid of those.
>
> Dale
>

If I had to guess I'd say, since this followed a power failure where
the machine was live and operating (if I've understood the thread
through a quick scan) that some file on disk has gotten corrupted and
it's that corruption that's causing the problem. You've checked
memory. Let's assume that te processor and MB weren't damaged by this
event. If that's the case - and unfortunately I don't know of any way
to ensure it hasn't as it requires one to have a bit-accurate image of
the machine before the power failure - there's probably no way to
eliminate this as a possibility short of an emerge -e @world.

It's not where I'd start. I'd probably look for core dump files or
very carefully do experiment s trying to isolate exactly what part of
KDE is firing off the problem. re-emerging the NVidia driver is a
no-brainer as it takes no more than 1-2 minutes to test things.
Rebuilding the machine is certainly more involved.

If you have lots of disk space you might rsync the whole machine to a
new partition to do the work, then using something other than KDE
which doesn't crash rebuild the copy from a chroot which leaves the
machine usable while the rebuild is going on.

None of this sounds like fun...

- Mark

Re: [gentoo-user] KDE and HARD lock ups.

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 976 bytes --]

On Wednesday 06 Jul 2011 12:38:22 Neil Bothwick wrote:
> On Wed, 6 Jul 2011 11:37:54 +0100, Mick wrote:
> > > It produces false positives and you need to look at the output for
> > > each affected package, but do you know a better way of detecting
> > > corruption of installed files?
> > 
> > I wasn't familiar with qcheck (yes, I know, I lead a sheltered life!)
> > but adding --verbose does not reveal additional info.  When you say
> > "look at the output", do you mean the output of emerge -1aDv <package> ?
> 
> The -B option restricts the output to just the names of packages with
> changed files. If you feed this list back to qcheck with just the -T
> option, you'll get a list of affected files.
> 
> qcheck -aBT >foo
> qcheck -T $(cat foo)
> 
> You may want to pipe the output from the second through grep -v /etc/

Very useful Neil, thanks!  Most of these files had lockfiles hanging around, 
or some changed config file.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Mark Knecht wrote:
>
> If I had to guess I'd say, since this followed a power failure where
> the machine was live and operating (if I've understood the thread
> through a quick scan) that some file on disk has gotten corrupted and
> it's that corruption that's causing the problem. You've checked
> memory. Let's assume that te processor and MB weren't damaged by this
> event. If that's the case - and unfortunately I don't know of any way
> to ensure it hasn't as it requires one to have a bit-accurate image of
> the machine before the power failure - there's probably no way to
> eliminate this as a possibility short of an emerge -e @world.
>
> It's not where I'd start. I'd probably look for core dump files or
> very carefully do experiment s trying to isolate exactly what part of
> KDE is firing off the problem. re-emerging the NVidia driver is a
> no-brainer as it takes no more than 1-2 minutes to test things.
> Rebuilding the machine is certainly more involved.
>
> If you have lots of disk space you might rsync the whole machine to a
> new partition to do the work, then using something other than KDE
> which doesn't crash rebuild the copy from a chroot which leaves the
> machine usable while the rebuild is going on.
>
> None of this sounds like fun...
>
> - Mark
>
>
>    

I did something similar at least.  I have two drives in here that are 
for my OS.  I have a third that is for data, videos, audio stuff and 
documents.  The data drive is a 750Gb.  The old main OS drive is a 160Gb 
and the spare OS drive is a 250Gb.  I downloaded a stage3 tarball.  I 
then set up the spare OS drive and mounted the partitions basically 
following the docs.  I then copied over /etc, disfiles and the world 
file.  After that, I did a emerge -e world which installed everything 
that I had before.  It also has a slightly newer kernel as well.

So, after running my memtest this morning while I took a nap, I booted 
into the new install.  I checked with the mount command to make sure I 
was in the new install too.  I deleted EVERYTHING KDE in my home 
directory.  After that, I logged into KDE.  A box popped up that 
composite was disabled.  It said I could hit shift alt F12 to enable.  
After I started Firefox, it locked up complete with my keyboard lights 
blinking again.

What does Fluxbox use as opposed to KDE?  Both use the Nvidia drivers 
right?  I use KDM for my login screen and I think nvidia is loaded when 
it starts and it uses nvidia thereafter.  So, if it was the driver, 
would it not mess up in Fluxbox too?   What makes Fluxbox work and KDE fail?

Could my video card be having issues?  I may take the sides off and 
unplug replug everything and give it all a once over.  Maybe just a bad 
connection or something.  Maybe?

If one of you guys were me, would you order a video card and try that?  
Keep in mind, I have surge protection inside the UPS on the wall side.  
I also have a surge protector strip that my modem, router, puter and 
monitor plugs into.  It's kind of hard to imagine that a surge could 
make it through all that and not at least smell up  the place a bit.  
I'm not saying it couldn't but just hard to imagine.  I got surge 
protection coming out the ears here.

Thoughts?

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Mark Knecht]

On Wed, Jul 6, 2011 at 3:00 PM, Dale <rdalek1967@gmail.com> wrote:
> Mark Knecht wrote:
>>
>> If I had to guess I'd say, since this followed a power failure where
>> the machine was live and operating (if I've understood the thread
>> through a quick scan) that some file on disk has gotten corrupted and
>> it's that corruption that's causing the problem. You've checked
>> memory. Let's assume that te processor and MB weren't damaged by this
>> event. If that's the case - and unfortunately I don't know of any way
>> to ensure it hasn't as it requires one to have a bit-accurate image of
>> the machine before the power failure - there's probably no way to
>> eliminate this as a possibility short of an emerge -e @world.
>>
>> It's not where I'd start. I'd probably look for core dump files or
>> very carefully do experiment s trying to isolate exactly what part of
>> KDE is firing off the problem. re-emerging the NVidia driver is a
>> no-brainer as it takes no more than 1-2 minutes to test things.
>> Rebuilding the machine is certainly more involved.
>>
>> If you have lots of disk space you might rsync the whole machine to a
>> new partition to do the work, then using something other than KDE
>> which doesn't crash rebuild the copy from a chroot which leaves the
>> machine usable while the rebuild is going on.
>>
>> None of this sounds like fun...
>>
>> - Mark
>>
>>
>>
>
> I did something similar at least.  I have two drives in here that are for my
> OS.  I have a third that is for data, videos, audio stuff and documents.
>  The data drive is a 750Gb.  The old main OS drive is a 160Gb and the spare
> OS drive is a 250Gb.  I downloaded a stage3 tarball.  I then set up the
> spare OS drive and mounted the partitions basically following the docs.  I
> then copied over /etc, disfiles and the world file.  After that, I did a
> emerge -e world which installed everything that I had before.  It also has a
> slightly newer kernel as well.
>
> So, after running my memtest this morning while I took a nap, I booted into
> the new install.  I checked with the mount command to make sure I was in the
> new install too.  I deleted EVERYTHING KDE in my home directory.  After
> that, I logged into KDE.  A box popped up that composite was disabled.  It
> said I could hit shift alt F12 to enable.  After I started Firefox, it
> locked up complete with my keyboard lights blinking again.
>
> What does Fluxbox use as opposed to KDE?  Both use the Nvidia drivers right?
>  I use KDM for my login screen and I think nvidia is loaded when it starts
> and it uses nvidia thereafter.  So, if it was the driver, would it not mess
> up in Fluxbox too?   What makes Fluxbox work and KDE fail?
>
> Could my video card be having issues?  I may take the sides off and unplug
> replug everything and give it all a once over.  Maybe just a bad connection
> or something.  Maybe?
>
> If one of you guys were me, would you order a video card and try that?  Keep
> in mind, I have surge protection inside the UPS on the wall side.  I also
> have a surge protector strip that my modem, router, puter and monitor plugs
> into.  It's kind of hard to imagine that a surge could make it through all
> that and not at least smell up  the place a bit.  I'm not saying it couldn't
> but just hard to imagine.  I got surge protection coming out the ears here.
>
> Thoughts?
>
> Dale

And this is your newer machine machine, correct? The one you built a
few months ago IIRC?

Sounds like you've takn the right steps to eliminate lots of problem
sites and it just isn't working. What a drag!

A machine lockup can come from almost anything not working. Bad
software is the easy one, but it could be hardware.

As for fluxbox vs KDE that's apples and oranges. They probably use
totally different parts of X and do it in very different ways. However
if fluxbox works perfectly for weeks then it wouldn't seem likely to
be a hardware issue unless it's a really unlikely corner case, but you
wouldn't think KDE would hit is every time and fluxbox never hits it.

Have you tried the most up to date ~amd64 drivers?

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Mark Knecht wrote:
> On Wed, Jul 6, 2011 at 3:00 PM, Dale<rdalek1967@gmail.com>  wrote:
>    
>> Mark Knecht wrote:
>>      
>>> If I had to guess I'd say, since this followed a power failure where
>>> the machine was live and operating (if I've understood the thread
>>> through a quick scan) that some file on disk has gotten corrupted and
>>> it's that corruption that's causing the problem. You've checked
>>> memory. Let's assume that te processor and MB weren't damaged by this
>>> event. If that's the case - and unfortunately I don't know of any way
>>> to ensure it hasn't as it requires one to have a bit-accurate image of
>>> the machine before the power failure - there's probably no way to
>>> eliminate this as a possibility short of an emerge -e @world.
>>>
>>> It's not where I'd start. I'd probably look for core dump files or
>>> very carefully do experiment s trying to isolate exactly what part of
>>> KDE is firing off the problem. re-emerging the NVidia driver is a
>>> no-brainer as it takes no more than 1-2 minutes to test things.
>>> Rebuilding the machine is certainly more involved.
>>>
>>> If you have lots of disk space you might rsync the whole machine to a
>>> new partition to do the work, then using something other than KDE
>>> which doesn't crash rebuild the copy from a chroot which leaves the
>>> machine usable while the rebuild is going on.
>>>
>>> None of this sounds like fun...
>>>
>>> - Mark
>>>
>>>
>>>
>>>        
>> I did something similar at least.  I have two drives in here that are for my
>> OS.  I have a third that is for data, videos, audio stuff and documents.
>>   The data drive is a 750Gb.  The old main OS drive is a 160Gb and the spare
>> OS drive is a 250Gb.  I downloaded a stage3 tarball.  I then set up the
>> spare OS drive and mounted the partitions basically following the docs.  I
>> then copied over /etc, disfiles and the world file.  After that, I did a
>> emerge -e world which installed everything that I had before.  It also has a
>> slightly newer kernel as well.
>>
>> So, after running my memtest this morning while I took a nap, I booted into
>> the new install.  I checked with the mount command to make sure I was in the
>> new install too.  I deleted EVERYTHING KDE in my home directory.  After
>> that, I logged into KDE.  A box popped up that composite was disabled.  It
>> said I could hit shift alt F12 to enable.  After I started Firefox, it
>> locked up complete with my keyboard lights blinking again.
>>
>> What does Fluxbox use as opposed to KDE?  Both use the Nvidia drivers right?
>>   I use KDM for my login screen and I think nvidia is loaded when it starts
>> and it uses nvidia thereafter.  So, if it was the driver, would it not mess
>> up in Fluxbox too?   What makes Fluxbox work and KDE fail?
>>
>> Could my video card be having issues?  I may take the sides off and unplug
>> replug everything and give it all a once over.  Maybe just a bad connection
>> or something.  Maybe?
>>
>> If one of you guys were me, would you order a video card and try that?  Keep
>> in mind, I have surge protection inside the UPS on the wall side.  I also
>> have a surge protector strip that my modem, router, puter and monitor plugs
>> into.  It's kind of hard to imagine that a surge could make it through all
>> that and not at least smell up  the place a bit.  I'm not saying it couldn't
>> but just hard to imagine.  I got surge protection coming out the ears here.
>>
>> Thoughts?
>>
>> Dale
>>      
> And this is your newer machine machine, correct? The one you built a
> few months ago IIRC?
>
> Sounds like you've takn the right steps to eliminate lots of problem
> sites and it just isn't working. What a drag!
>
> A machine lockup can come from almost anything not working. Bad
> software is the easy one, but it could be hardware.
>
> As for fluxbox vs KDE that's apples and oranges. They probably use
> totally different parts of X and do it in very different ways. However
> if fluxbox works perfectly for weeks then it wouldn't seem likely to
> be a hardware issue unless it's a really unlikely corner case, but you
> wouldn't think KDE would hit is every time and fluxbox never hits it.
>
> Have you tried the most up to date ~amd64 drivers?
>
>
>    

Let me add some more confusion.  I'm in KDE right now.  I took the sides 
off and blew out a VERY little bit of dust and replugged things, video 
card, mobo power cables and such as that.  I also booted to the newly 
created .kde directory instead of my old one.  This is the old install 
tho.  I logged in with nothing running, blank session, and then took a 
nap.  I got up a few minutes ago and KDE is still running.  I opened 
Kpat, card game, and played a little of it.  After a few minutes, I 
opened Seamonkey and am typing as you can see.  Same kernel, same 
nvidia, same packages and same hardware.

I did notice something a bit ago but have not posted since I noticed 
it.  It seems to crash when I open Konsole as root.  I have my menu set 
up to run it as root and that is where I do my sync and updates.  As 
soon as the window pops up, my mouse pointer freezes.  I thought it was 
a coincidence until now.  After I send this reply, I'm going to open 
Konsole and nothing else.  I want to see if it does it again.  Since it 
has been running this long with Konsole closed, it would be odd if it 
fails when I open that up here shortly.

I have tried to eliminate things one by one.  I tried a different kernel 
before I ever posted anything but I'm not sure I mentioned it.  Doing 
that is almost like breathing.  If I run into issues, I try a old kernel 
first.  I have also tried both nvidia drivers that are in portage with a 
few different kernels.  As mentioned, I also tried a fresh install as 
well.  This makes me question hardware but since everything has to work 
together, who knows where to start.  Could it be the extra ram that 
Konsole accesses?  Could it be a bad instruction that the CPU doesn't 
like?  Could it be the video card trying to redraw the screen?  Lots of 
questions with few answers.

Well, I'm going to send this then open Konsole.  See if it locks up again.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Dale wrote:
>
> Let me add some more confusion.  I'm in KDE right now.  I took the 
> sides off and blew out a VERY little bit of dust and replugged things, 
> video card, mobo power cables and such as that.  I also booted to the 
> newly created .kde directory instead of my old one.  This is the old 
> install tho.  I logged in with nothing running, blank session, and 
> then took a nap.  I got up a few minutes ago and KDE is still 
> running.  I opened Kpat, card game, and played a little of it.  After 
> a few minutes, I opened Seamonkey and am typing as you can see.  Same 
> kernel, same nvidia, same packages and same hardware.
>
> I did notice something a bit ago but have not posted since I noticed 
> it.  It seems to crash when I open Konsole as root.  I have my menu 
> set up to run it as root and that is where I do my sync and updates.  
> As soon as the window pops up, my mouse pointer freezes.  I thought it 
> was a coincidence until now.  After I send this reply, I'm going to 
> open Konsole and nothing else.  I want to see if it does it again.  
> Since it has been running this long with Konsole closed, it would be 
> odd if it fails when I open that up here shortly.
>
> I have tried to eliminate things one by one.  I tried a different 
> kernel before I ever posted anything but I'm not sure I mentioned it.  
> Doing that is almost like breathing.  If I run into issues, I try a 
> old kernel first.  I have also tried both nvidia drivers that are in 
> portage with a few different kernels.  As mentioned, I also tried a 
> fresh install as well.  This makes me question hardware but since 
> everything has to work together, who knows where to start.  Could it 
> be the extra ram that Konsole accesses?  Could it be a bad instruction 
> that the CPU doesn't like?  Could it be the video card trying to 
> redraw the screen?  Lots of questions with few answers.
>
> Well, I'm going to send this then open Konsole.  See if it locks up 
> again.
>
> Dale
>
> :-)  :-)
>

I forgot to answer one question you had.  Yes, this is my new rig that 
was built a while back.

As I was suspecting, I opened Konsole after sending the last message and 
it locked up real good.  I did manage to get the SysReq keys to work 
tho.  I opened Konsole from the menu, the password window popped up and 
I typed in my root password.  After that, the Konsole window popped up 
and as soon as I touched the mouse, lock up.

After I rebooted and logged in, I wanted to see if it could be a bad 
memory issue or even the video card itself.  I opened a HD video, 
Asteroid Galaxy Tour, and played it back to back.  It never missed a 
beat.  I'm going to avoid Konsole and see what all else I can open until 
it fails again.  I'll post back what happens.

Any of you gurus figure out why my system hates to open Konsole as 
root?  I might add, I used konsole from inside Fluxbox with no problems.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Dale wrote:
> Dale wrote:
>>
>> Let me add some more confusion.  I'm in KDE right now.  I took the 
>> sides off and blew out a VERY little bit of dust and replugged 
>> things, video card, mobo power cables and such as that.  I also 
>> booted to the newly created .kde directory instead of my old one.  
>> This is the old install tho.  I logged in with nothing running, blank 
>> session, and then took a nap.  I got up a few minutes ago and KDE is 
>> still running.  I opened Kpat, card game, and played a little of it.  
>> After a few minutes, I opened Seamonkey and am typing as you can 
>> see.  Same kernel, same nvidia, same packages and same hardware.
>>
>> I did notice something a bit ago but have not posted since I noticed 
>> it.  It seems to crash when I open Konsole as root.  I have my menu 
>> set up to run it as root and that is where I do my sync and updates.  
>> As soon as the window pops up, my mouse pointer freezes.  I thought 
>> it was a coincidence until now.  After I send this reply, I'm going 
>> to open Konsole and nothing else.  I want to see if it does it 
>> again.  Since it has been running this long with Konsole closed, it 
>> would be odd if it fails when I open that up here shortly.
>>
>> I have tried to eliminate things one by one.  I tried a different 
>> kernel before I ever posted anything but I'm not sure I mentioned 
>> it.  Doing that is almost like breathing.  If I run into issues, I 
>> try a old kernel first.  I have also tried both nvidia drivers that 
>> are in portage with a few different kernels.  As mentioned, I also 
>> tried a fresh install as well.  This makes me question hardware but 
>> since everything has to work together, who knows where to start.  
>> Could it be the extra ram that Konsole accesses?  Could it be a bad 
>> instruction that the CPU doesn't like?  Could it be the video card 
>> trying to redraw the screen?  Lots of questions with few answers.
>>
>> Well, I'm going to send this then open Konsole.  See if it locks up 
>> again.
>>
>> Dale
>>
>> :-)  :-)
>>
>
> I forgot to answer one question you had.  Yes, this is my new rig that 
> was built a while back.
>
> As I was suspecting, I opened Konsole after sending the last message 
> and it locked up real good.  I did manage to get the SysReq keys to 
> work tho.  I opened Konsole from the menu, the password window popped 
> up and I typed in my root password.  After that, the Konsole window 
> popped up and as soon as I touched the mouse, lock up.
>
> After I rebooted and logged in, I wanted to see if it could be a bad 
> memory issue or even the video card itself.  I opened a HD video, 
> Asteroid Galaxy Tour, and played it back to back.  It never missed a 
> beat.  I'm going to avoid Konsole and see what all else I can open 
> until it fails again.  I'll post back what happens.
>
> Any of you gurus figure out why my system hates to open Konsole as 
> root?  I might add, I used konsole from inside Fluxbox with no problems.
>
> Dale
>
> :-)  :-)
>

A little more info.  After my last message, I opened Firefox.  It locked 
up.  That runs as a regular user of course.  So, I wanted to test a 
theory.  I logged into Fluxbox after my reboot.  I opened Firefox and it 
locked up.  Nothing else was running.  My first lock up in Fluxbox!!

So, Firefox will lock up in BOTH KDE and Fluxbox.  What do Konsole in 
KDE, Fluxbox in both KDE and Fluxbox have in common?   Keep in mind, 
Konsole works fine in Fluxbox.

I thought of something tho.  I upgraded glibc a while back.  I had some 
KDE updates and a Firefox update just a little bit before this 
happened.  Could this be related somehow?

Also, when Firefox locked up, I went to my old rig and tried to login to 
this rig.  The network connection was dead.  So, that time at least, it 
was a serious lock up.  Sometimes the SysReq keys work, sometimes not.

Thoughts?  Anyone think of anything that could cause this?

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[William Kenworthy]

On Wed, 2011-07-06 at 23:01 -0500, Dale wrote:
> Dale wrote:
> > Dale wrote:
> >>
> Thoughts?  Anyone think of anything that could cause this?
> 
> Dale
> 
> :-)  :-)
> 

Hi Dale, I have not been following the thread, but have you tried
starting the problem apps, konsole etc from a basic xterm with strace?

BillK



-- 
William Kenworthy <billk@iinet.net.au>
Home in Perth!

Re: [gentoo-user] KDE and HARD lock ups.

[Jesús J. Guerrero Botella]

2011/7/6 Dale <rdalek1967@gmail.com>:
> Jesús J. Guerrero Botella wrote:
>>
>> Dale, random hard-lockups are only due to hardware or kerne, it can't
>> be otherwisel (drivers count as part of kernel). The fact that
>> compilation doesn't lock your system only means that the thing
>> (whatever it is) is not bount to intensive I/O operations and/or high
>> cpu loads.
>>
>> Openldap itself can't hard lock up anything if the kernel doesn't give
>> it permissions to do so (kernel bug) or if the hardware is not faulty.
>> Same goes for tray apps.
>>
>>
>
> OK.  I tested this and it doesn't help any.  I tried three different
> kernels, all of which I have used in the past with no problems, and get the
> same thing.  I have tried reinstalling nvidia-drivers and a different
> versions of nvidia-drivers, same thing.  So, either previously working
> kernels are now broke, nvidia which was working fine just a few days ago
> with no recent updates here just broke or just maybe it is something else we
> have yet to figure out yet.  I also ran memtest for HOURS with not one
> problem reported.
>
> Given I have tried the above, do you still think it is kernel, nvidia or
> hardware?  I'm about to run tests on the drive now.  I suspect it is going
> to show no problems as well.

I can't know what it is, but all the kernels you list are .38, and all
of them are affected by the bug I described, so you haven't discarded
anything yet. Try 2.6.39.2 if you want to discard that.

All the drivers you've tried are also the same nvidia-drivers, so
that's a poor attempt as well. Try vesa, as said.

All I say is that user land applications CAN'T hard lock the whole OS
unless the kernel let's them do so. And that can only happens because
of three reasons:

a) kernel bug
b) drivers
c) hardware

Unless it's not truly a hard-lock, in which case the title of the
thread is misleading.

> I did try .39 but it had issues.  I got rid of those.

Right, but .38 suffers the bug we are telling you. So you'll have to
fix these issues, or you'll never discard the possibility that's the
USB bug from .38 bitting you.

-- 
Jesús Guerrero Botella

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

William Kenworthy wrote:
> On Wed, 2011-07-06 at 23:01 -0500, Dale wrote:
>    
>> Dale wrote:
>>      
>>> Dale wrote:
>>>        
>>>>          
>> Thoughts?  Anyone think of anything that could cause this?
>>
>> Dale
>>
>> :-)  :-)
>>
>>      
> Hi Dale, I have not been following the thread, but have you tried
> starting the problem apps, konsole etc from a basic xterm with strace?
>
> BillK
>
>    

That's a thought.  I happened to already have a Konsole open in Fluxbox 
so I typed in Firefox.  It started then locked up Fluxbox.  I could 
still see the Konsole screen and nothing was printed as far as error 
messages.  I'm not sure I can tell anything with strace.  I'm not sure I 
will be able to see the messages enough to see what happens.  Since the 
GUI locks up, I can't move things around or save the errors either.

It's a good idea tho.  I'm just not sure how to skin this little kitty.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Jesús J. Guerrero Botella wrote:
> 2011/7/6 Dale<rdalek1967@gmail.com>:
>    
>> Jesús J. Guerrero Botella wrote:
>>      
>>> Dale, random hard-lockups are only due to hardware or kerne, it can't
>>> be otherwisel (drivers count as part of kernel). The fact that
>>> compilation doesn't lock your system only means that the thing
>>> (whatever it is) is not bount to intensive I/O operations and/or high
>>> cpu loads.
>>>
>>> Openldap itself can't hard lock up anything if the kernel doesn't give
>>> it permissions to do so (kernel bug) or if the hardware is not faulty.
>>> Same goes for tray apps.
>>>
>>>
>>>        
>> OK.  I tested this and it doesn't help any.  I tried three different
>> kernels, all of which I have used in the past with no problems, and get the
>> same thing.  I have tried reinstalling nvidia-drivers and a different
>> versions of nvidia-drivers, same thing.  So, either previously working
>> kernels are now broke, nvidia which was working fine just a few days ago
>> with no recent updates here just broke or just maybe it is something else we
>> have yet to figure out yet.  I also ran memtest for HOURS with not one
>> problem reported.
>>
>> Given I have tried the above, do you still think it is kernel, nvidia or
>> hardware?  I'm about to run tests on the drive now.  I suspect it is going
>> to show no problems as well.
>>      
> I can't know what it is, but all the kernels you list are .38, and all
> of them are affected by the bug I described, so you haven't discarded
> anything yet. Try 2.6.39.2 if you want to discard that.
>
> All the drivers you've tried are also the same nvidia-drivers, so
> that's a poor attempt as well. Try vesa, as said.
>
> All I say is that user land applications CAN'T hard lock the whole OS
> unless the kernel let's them do so. And that can only happens because
> of three reasons:
>
> a) kernel bug
> b) drivers
> c) hardware
>
> Unless it's not truly a hard-lock, in which case the title of the
> thread is misleading.
>
>    
>> I did try .39 but it had issues.  I got rid of those.
>>      
> Right, but .38 suffers the bug we are telling you. So you'll have to
> fix these issues, or you'll never discard the possibility that's the
> USB bug from .38 bitting you.
>
>    

You have a good point but there is a problem.  Some of the kernels I 
tried ran on this machine with uptimes of several weeks and not one lock 
up.  It could be some upgrade that affected this but who knows what that 
was since I have updated a lot.  As for nvidia, I tried both versions 
that work with my card that are in portage.  I got the same with that no 
matter what I tried.

As for .39 kernels, I mentioned in this mess somewhere that I had 
upgraded but ran into problems with that series so I deleted them.  I 
may just be adding to the problems I am having if I do upgrade again.  
But since I got to try something, I'll try the latest .39 and see what 
it does.

I remember having this type of problem once before.  It turned out to be 
a gcc problem if I recall correctly.  I went back a version of gcc and 
then did a emerge -e world.  After that, things worked fine.  Thing is, 
I have had the same gcc since I built this rig according to genlop.

Weird.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Dale wrote:
>
> You have a good point but there is a problem.  Some of the kernels I 
> tried ran on this machine with uptimes of several weeks and not one 
> lock up.  It could be some upgrade that affected this but who knows 
> what that was since I have updated a lot.  As for nvidia, I tried both 
> versions that work with my card that are in portage.  I got the same 
> with that no matter what I tried.
>
> As for .39 kernels, I mentioned in this mess somewhere that I had 
> upgraded but ran into problems with that series so I deleted them.  I 
> may just be adding to the problems I am having if I do upgrade again.  
> But since I got to try something, I'll try the latest .39 and see what 
> it does.
>
> I remember having this type of problem once before.  It turned out to 
> be a gcc problem if I recall correctly.  I went back a version of gcc 
> and then did a emerge -e world.  After that, things worked fine.  
> Thing is, I have had the same gcc since I built this rig according to 
> genlop.
>
> Weird.
>
> Dale
>
> :-)  :-)
>

I tried the latest .39 kernel.  It does the exact same thing as a .38 
kernel.  I also tried a kernel that was the first one I made when I 
built this rig.  It locked up as well.  It appears to me that either 
every single kernel, including ones that worked fine before, are either 
broke or it is not related to the kernel itself.  I'm starting to bet on 
the last one.

I did notice one thing tho.  When I tried to emerge the nvidia drivers 
for the .39 kernel, emerge wanted to DOWNGRADE glibc.  This ain't my 
first trip to Linux land.  Can someone explain to me why the heck emerge 
wants to do something as crazy as that?  I think every one here knows 
that is a really bad thing to even think of much less actually try.  Is 
it possible that something in glibc is causing trouble and this is 
someone's wet dream to fix it?

Thanks.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Mark Knecht]

On Wed, Jul 6, 2011 at 9:01 PM, Dale <rdalek1967@gmail.com> wrote:
<SNIP>
> A little more info.  After my last message, I opened Firefox.  It locked up.
>  That runs as a regular user of course.  So, I wanted to test a theory.  I
> logged into Fluxbox after my reboot.  I opened Firefox and it locked up.
>  Nothing else was running.  My first lock up in Fluxbox!!
>
> So, Firefox will lock up in BOTH KDE and Fluxbox.  What do Konsole in KDE,
> Fluxbox in both KDE and Fluxbox have in common?   Keep in mind, Konsole
> works fine in Fluxbox.
>
> I thought of something tho.  I upgraded glibc a while back.  I had some KDE
> updates and a Firefox update just a little bit before this happened.  Could
> this be related somehow?
>
> Also, when Firefox locked up, I went to my old rig and tried to login to
> this rig.  The network connection was dead.  So, that time at least, it was
> a serious lock up.  Sometimes the SysReq keys work, sometimes not.
>
> Thoughts?  Anyone think of anything that could cause this?
>
> Dale
>
> :-)  :-)
>
>

You should continue to investigate the glibc thing. There was a thread
about how it's causing problems for someone running LibreOffice I
think.

You might also look more at what part of Firefox s causing the lockup.
Is it Firefox proper, or is it something caused by your homepage? For
instance, if they make use of Flash or Java it could be one of them
causing the lockup and not specifically Firefox itself. Can yo erase
Firefox preferences so that it opes to a blank page. Does it still
lock up. Have you removed all cookies, etc., to see if one of them is
causing the problems. Since fluxbox doesn't crash as often you might
work there to clean things up and then come back to KDE to see if it
has helped.

Consider an emerge -C on things you don't absolutely need, like Flash
or whatever you're using, to figure out what's involved. Also, are you
using Firefox 3 or 4? Consider trying the other.

As with other apps, try running Firefox from a terminal and see if it
throws any error messages.

Good luck,
Mark

Re: [gentoo-user] KDE and HARD lock ups.

[Robin Atwood]

On Thursday 07 Jul 2011, Dale wrote:

> Well, I'm going to send this then open Konsole.  See if it locks up again.

There was a fairly well documented problem, on the Gentoo fora at least, with 
the nvidia drivers, Xorg-server-1.10, KDE 4.6 and Konsole. I had it on several 
machines that locked up as soon as you resized konsole. The solution was to 
fall-back to Xorg 1.9 server and drivers. However, with the latest Xorg 
drivers and nvidia drivers, the problem is solved:

[I] x11-base/xorg-drivers (1.11@01/07/11): Meta package containing deps on all 
xorg drivers
[I] x11-base/xorg-server (1.10.2@25/06/11): X.Org X servers
[I] x11-drivers/nvidia-drivers (275.09.07@25/06/11): NVIDIA X11 driver and GLX 
libraries

I am running kernel 2.6.39-r2 but i don't believe that is critical.

HTH
-Robin
-- 
----------------------------------------------------------------------
Robin Atwood.

"Ship me somewheres east of Suez, where the best is like the worst,
 Where there ain't no Ten Commandments an' a man can raise a thirst"
         from "Mandalay" by Rudyard Kipling
----------------------------------------------------------------------









-- 
------------------------------------------------------
Robin Atwood.
mobile:	+91 9986 037121
------------------------------------------------------

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Mark Knecht wrote:
>
> You should continue to investigate the glibc thing. There was a thread
> about how it's causing problems for someone running LibreOffice I
> think.
>
> You might also look more at what part of Firefox s causing the lockup.
> Is it Firefox proper, or is it something caused by your homepage? For
> instance, if they make use of Flash or Java it could be one of them
> causing the lockup and not specifically Firefox itself. Can yo erase
> Firefox preferences so that it opes to a blank page. Does it still
> lock up. Have you removed all cookies, etc., to see if one of them is
> causing the problems. Since fluxbox doesn't crash as often you might
> work there to clean things up and then come back to KDE to see if it
> has helped.
>
> Consider an emerge -C on things you don't absolutely need, like Flash
> or whatever you're using, to figure out what's involved. Also, are you
> using Firefox 3 or 4? Consider trying the other.
>
> As with other apps, try running Firefox from a terminal and see if it
> throws any error messages.
>
> Good luck,
> Mark
>
>
>    


I haven't been ignoring your suggestions but I did try them a bit ago.  
It's in another reply.  Thanks for the suggestions tho.

As for trying to run from a terminal, if I do that, I can't see the 
errors and when the kernel panics, I lose the messages.  Sort of a catch 
22 here.  Would be nice if I could tho.

Thanks.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[Dale]

Robin Atwood wrote:
> On Thursday 07 Jul 2011, Dale wrote:
>
>    
>> Well, I'm going to send this then open Konsole.  See if it locks up again.
>>      
> There was a fairly well documented problem, on the Gentoo fora at least, with
> the nvidia drivers, Xorg-server-1.10, KDE 4.6 and Konsole. I had it on several
> machines that locked up as soon as you resized konsole. The solution was to
> fall-back to Xorg 1.9 server and drivers. However, with the latest Xorg
> drivers and nvidia drivers, the problem is solved:
>
> [I] x11-base/xorg-drivers (1.11@01/07/11): Meta package containing deps on all
> xorg drivers
> [I] x11-base/xorg-server (1.10.2@25/06/11): X.Org X servers
> [I] x11-drivers/nvidia-drivers (275.09.07@25/06/11): NVIDIA X11 driver and GLX
> libraries
>
> I am running kernel 2.6.39-r2 but i don't believe that is critical.
>
> HTH
> -Robin
>    

This appears to have fixed the problem with me opening Konsole.  I went 
back to 1.9 series and all is well with Konsole at least.  Now to figure 
out Firefox.

Thanks.

Dale

:-)  :-)

Re: [gentoo-user] KDE and HARD lock ups.

[William Kenworthy]

firefox --help lists a DISPLAY option.  Start it from a console and set
$DISPLAY elsewhere, even remote if thats what it takes ...


BillK


On Fri, 2011-07-08 at 20:53 -0500, Dale wrote:
> Mark Knecht wrote:
> >
> > You should continue to investigate the glibc thing. There was a thread
> > about how it's causing problems for someone running LibreOffice I
> > think.
> >
> > You might also look more at what part of Firefox s causing the lockup.
> > Is it Firefox proper, or is it something caused by your homepage? For
> > instance, if they make use of Flash or Java it could be one of them
> > causing the lockup and not specifically Firefox itself. Can yo erase
> > Firefox preferences so that it opes to a blank page. Does it still
> > lock up. Have you removed all cookies, etc., to see if one of them is
> > causing the problems. Since fluxbox doesn't crash as often you might
> > work there to clean things up and then come back to KDE to see if it
> > has helped.
> >
> > Consider an emerge -C on things you don't absolutely need, like Flash
> > or whatever you're using, to figure out what's involved. Also, are you
> > using Firefox 3 or 4? Consider trying the other.
> >
> > As with other apps, try running Firefox from a terminal and see if it
> > throws any error messages.
> >
> > Good luck,
> > Mark
> >
> >
> >    
> 
> 
> I haven't been ignoring your suggestions but I did try them a bit ago.  
> It's in another reply.  Thanks for the suggestions tho.
> 
> As for trying to run from a terminal, if I do that, I can't see the 
> errors and when the kernel panics, I lose the messages.  Sort of a catch 
> 22 here.  Would be nice if I could tho.
> 
> Thanks.
> 
> Dale
> 
> :-)  :-)
> 

-- 
William Kenworthy <billk@iinet.net.au>
Home in Perth!