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
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
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
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?
2011/7/6 Dale rdalek1...@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
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
Jesús J. Guerrero Botella wrote:
2011/7/6 Dalerdalek1...@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
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
On Wed, Jul 6, 2011 at 9:01 PM, Dale rdalek1...@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.
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
Paul Hartman wrote:
On Tue, Jul 5, 2011 at 11:16 PM, Dalerdalek1...@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
On Wed, Jul 6, 2011 at 12:12 AM, Dale rdalek1...@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,
Paul Hartman wrote:
On Wed, Jul 6, 2011 at 12:12 AM, Dalerdalek1...@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,
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
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
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
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
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.
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
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
On Wed, 06 Jul 2011 03:53:23 -0500
Dale rdalek1...@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
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
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
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
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
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
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
On Wed, Jul 6, 2011 at 7:44 AM, Peter Humphrey pe...@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
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
On Wed, Jul 6, 2011 at 12:27 PM, Dale rdalek1...@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
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
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.
On Wed, Jul 6, 2011 at 3:00 PM, Dale rdalek1...@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
Mark Knecht wrote:
On Wed, Jul 6, 2011 at 3:00 PM, Dalerdalek1...@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
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
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
2011/7/5 Dale rdalek1...@gmail.com:
Jesús J. Guerrero Botella wrote:
2011/7/4 Dalerdalek1...@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
Jesús J. Guerrero Botella wrote:
2011/7/5 Dalerdalek1...@gmail.com:
Jesús J. Guerrero Botella wrote:
2011/7/4 Dalerdalek1...@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
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
On Tue, Jul 5, 2011 at 2:23 PM, Dale rdalek1...@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
Paul Hartman wrote:
On Tue, Jul 5, 2011 at 2:23 PM, Dalerdalek1...@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.
Dale wrote:
Paul Hartman wrote:
On Tue, Jul 5, 2011 at 2:23 PM, Dalerdalek1...@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
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
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
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
On Tue, Jul 5, 2011 at 6:04 PM, Neil Bothwick n...@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.
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
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
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
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
On Tue, Jul 5, 2011 at 6:49 PM, Neil Bothwick n...@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
On Tue, Jul 5, 2011 at 11:16 PM, Dale rdalek1...@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
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
2011/7/4 Dale rdalek1...@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
Jesús J. Guerrero Botella wrote:
2011/7/4 Dalerdalek1...@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
On Monday 04 July 2011 19:12:50 Jesús J. Guerrero Botella did opine
thusly:
2011/7/4 Dale rdalek1...@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
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
Alan McKinnon wrote:
On Monday 04 July 2011 19:12:50 Jesús J. Guerrero Botella did opine
thusly:
2011/7/4 Dalerdalek1...@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
2011/7/4 Dale rdalek1...@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
Jesús J. Guerrero Botella wrote:
2011/7/4 Dalerdalek1...@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
Jesús J. Guerrero Botella jesus.guerrero.bote...@gmail.com wrote:
2011/7/4 Dale rdalek1...@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
Gregory Shearman wrote:
Jesús J. Guerrero Botellajesus.guerrero.bote...@gmail.com wrote:
2011/7/4 Dalerdalek1...@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
62 matches
Mail list logo
