-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Saturday 2007-12-22 at 20:41 +0100, I wrote:
The Thursday 2007-12-20 at 08:09 +0800, Joe Morris (NTM) wrote:
I would therefore suggest to pass cpufreq=no as a boot argument, and use
Tried that, yesterday. All went fine, till a minute ago,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-20 at 08:09 +0800, Joe Morris (NTM) wrote:
I would therefore suggest to pass cpufreq=no as a boot argument, and use
Tried that, yesterday. All went fine, till a minute ago, it freezed. A
key (shift), and it waked up. So, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-20 at 08:53 +0800, Joe Morris (NTM) wrote:
On 12/20/2007 08:25 AM, Carlos E. R. wrote:
After what jiffies did, I wouldn't. Is this your system with xfs? Just
trying not to offer bad advice.
As a matter of fact, I do hav
On 12/20/2007 08:25 AM, Carlos E. R. wrote:
>
> > After what jiffies did, I wouldn't. Is this your system with xfs? Just
> > trying not to offer bad advice.
>
> As a matter of fact, I do have some xfs partitions in my system, but
> not the root. Why? Do you think that clock problems can cause pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-20 at 08:09 +0800, Joe Morris (NTM) wrote:
I would therefore suggest to pass cpufreq=no as a boot argument, and use
tsc, to see if that allows your clock to work correctly, without a cpu
frequency change perhaps causing a "laz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Thursday 2007-12-20 at 08:09 +0800, Joe Morris (NTM) wrote:
Is no good.
* acpi_pm looses time, like several minutes per hour.
* tsc "appears" to work well, but might be suspicious
According to an error message on my system, I think your c
On 12/20/2007 01:32 AM, Carlos E. R. wrote:
> I just tried, and my system crashed:
>
> echo jiffies >
> /sys/devices/system/clocksource/clocksource0/current_clocksource
>
>
> I tried again, in runlevel 3, and I discovered that the clock stopped.
> I tried again to go back to tsc, but the clock cont
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Tuesday 2007-12-18 at 07:27 +0800, Joe Morris (NTM) wrote:
But I refuse to believe it can be a hardware problem, because 10.2 had
no problems, and the problems started as soon as I upgraded to 10.3
Maybe it is not indicating a hardware failu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Tuesday 2007-12-18 at 17:53 +0100, Rikard Johnels wrote:
What services etc do you have running?
What software is running?
The default services that come with the distro, mostly. Nothing weird. This
is a desktop machine. There is amavis, pos
On Tuesday 18 December 2007 16:30, Carlos E. R. wrote:
> The Tuesday 2007-12-18 at 07:36 -0600, David C. Rankin wrote:
> > Carlos,
> >
> > There has to be an interrupt sharing conflict somewhere. Can you
> > disable some hardware and see if it stops. (unplug usb devices, pull the
> > sound card
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Tuesday 2007-12-18 at 07:36 -0600, David C. Rankin wrote:
Carlos,
There has to be an interrupt sharing conflict somewhere. Can you
disable some hardware and see if it stops. (unplug usb devices, pull the
sound card, etc..) If it does,
Carlos E. R. wrote:
>
>
> The Monday 2007-12-17 at 15:18 +0100, Carlos E. R. wrote:
>
>> The Sunday 2007-12-16 at 21:29 -0600, David C. Rankin wrote:
>
>>> Other than that, just set the clock to show seconds and forget
>>> about
>>> it ;-)
>
>> Tried that too.
>
>> But gkrelmn does upda
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Monday 2007-12-17 at 15:18 +0100, Carlos E. R. wrote:
The Sunday 2007-12-16 at 21:29 -0600, David C. Rankin wrote:
Other than that, just set the clock to show seconds and forget about
it ;-)
Tried that too.
But gkrelmn does upda
On Mon, 2007-12-17 at 15:19 +0100, Carlos E. R. wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dificult to say, yes.
>
> - --
> Cheers,
> Carlos E. R.
I know...coincidence or the twilight zone...after 52 hours, all is well
here, on one EIDE and one SADA drive. Only thing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Tuesday 2007-12-18 at 07:27 +0800, Joe Morris (NTM) wrote:
But I refuse to believe it can be a hardware problem, because 10.2 had
no problems, and the problems started as soon as I upgraded to 10.3
Maybe it is not indicating a hardware failu
On 12/17/2007 10:20 PM, Carlos E. R. wrote:
>
>
> The Monday 2007-12-17 at 06:04 -0700, Jc Polanycia wrote:
>
> > I have seen this type of behavior once before on one of our Sparc
> boxes. It
> > would randomly stop processing, then wake up. You could watch the clock
> > stop ticking and then sta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Monday 2007-12-17 at 06:04 -0700, Jc Polanycia wrote:
I have seen this type of behavior once before on one of our Sparc boxes. It
would randomly stop processing, then wake up. You could watch the clock
stop ticking and then start again. Som
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Sunday 2007-12-16 at 21:11 -0700, Tom Patton wrote:
This thread is sounding suspiciously similar to my drive failure
Thursday, following a YOU last weekend. See my thread "ata2 suddenly
bad". I mean the randomly "sluggish" aka "lock-up" synd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Sunday 2007-12-16 at 21:29 -0600, David C. Rankin wrote:
inactive for:" is set to "Never" (and the minimum period possible is 11
minutes). And both the power and suspend buttons are set to trigger
"hibernate".
Try setting "Never" to
I have seen this type of behavior once before on one of our Sparc boxes. It
would randomly stop processing, then wake up. You could watch the clock
stop ticking and then start again. Some applications (that weren't looking
for a clock tick) would be okay, but others (like Kerberos, for some
On Mon, 2007-12-17 at 02:17 +0100, Carlos E. R. wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> The Sunday 2007-12-16 at 16:28 -0800, Linda Walsh wrote:
>
>
> However, I think I had instances of these freezing episodes weeks ago,
> before I set the 'tsc' clock, so...
>
> I
Carlos E. R. wrote:
>
>
> The Sunday 2007-12-16 at 14:28 -0800, Linda Walsh wrote:
>
>> It _sounds_ like some power-saving feature is set to become
>> "active" a short time after last user input (also sounds like it might
>> be messing up; but it could be a 'feature' for some people (on lapt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Sunday 2007-12-16 at 16:28 -0800, Linda Walsh wrote:
Good idea... but it doesn't appear to be that easy.
---
Never is :-(.
It would likely be at the kernel level - like the kernel is going into
a "low-load" setting -- since your sy
Carlos E. R. wrote:
The Sunday 2007-12-16 at 14:28 -0800, Linda Walsh wrote:
It _sounds_ like some power-saving feature is set to become
"active" a short time after last user input (also sounds like it might
be messing up; but it could be a 'feature' for some people (on laptop,
on battery po
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Sunday 2007-12-16 at 20:29 +0100, Rikard Johnels wrote:
Revert back to runlevel 3 and see if the system still is "lazy".
Check the syslog for errors.
Report back.
If I go to a text console, in level 5, it appears not to go lazy, but it
is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Sunday 2007-12-16 at 14:28 -0800, Linda Walsh wrote:
It _sounds_ like some power-saving feature is set to become
"active" a short time after last user input (also sounds like it might
be messing up; but it could be a 'feature' for some
Carlos E. R. wrote:
I go to ctrl-alt-f1, start there "top", and it works. I go back to the
desktop (gnome) and the laziness seems gone. As I'm writing this, I stop
that 'top', and the desktop continues working - no, it doesn't, it stops
after 10" or so.
I set the clock to show seconds, it wor
mber 2007 1:03 a.m.
> To: OS
> Subject: [opensuse] My desktop has become "lazy" lately
>
>
>
> Hi,
>
> That's the best description, its become lazy. Some times, if I'm not
> typing or moving the mouse, the entire machine stops. I see the display of
> gkre
Sounds to me like your system is only working when being external interrupts
are present. How to solve, beats me.
-Original Message-
From: Carlos E. R. [mailto:[EMAIL PROTECTED]
Sent: Monday, 17 December 2007 1:03 a.m.
To: OS
Subject: [opensuse] My desktop has become "lazy&qu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
That's the best description, its become lazy. Some times, if I'm not
typing or moving the mouse, the entire machine stops. I see the display of
gkrelmn stop. I was calculating the size of a directory using 'mc', went
out for an hour, and the
30 matches
Mail list logo
