On 2013-12-23 22:36, Batman13 wrote:
> thank you so much for your answer , yes its exactly as you describe … I
> am waiting to know how you did to trick the machine …
> if you have a script or something just post it … thank you again i
> didnt expect people to reply so quickly …
Comment: you do not need to send me a PM with the contents of the reply on the thread. If my
computer is working as it should, I notice the posts
Ok, at least in my case any interrupt signal would keep awake the computer for some seconds, like a
keypress, a mouse movement, a mouse click… but also something on the network (an incoming network
packet generates an interrupt). So what I did was log into my router, which happens to be an
embedded Linux machine, and send a ping every second to my computer, forever. This was enough to
keep it awake. Of course, I had to do it every time I booted it… which was a nuisance. I was able
to automate the procedure a bit, but not much.
On the other hand, I also opened a Bugzilla at Novell, against the kernel. To prove the issue, I did
a script that… let me see if I can remember. It was a one second delay loop, and on every
iteration it checked how much time has passed since the previous iteration. If it was 2 seconds or
more, it wrote the timestamp and time difference to a file.
The result is a log file with entries every time the machine stopped processing, specifying for how
long it stopped. I proved there could be delays of several minutes.
Of course, at least in my case, the clock worked correctly: after every “freeze”, it would still
show the correct time to the second.
I suppose I could dig out those scripts. I also did a pascal program to do it better. I must have it
In my case the issue ended because I bought another computer or with a kernel change, or both
things. Maybe it was never solved, and I was the only one on the entire Earth suffering it, it
seemed. Now there are two people… :-}
But I would need to upgrade that machine again to see if my machine is still affected, which is very
problematic to do.
I’ll try to find out the bug number. If I forget to tell you this data (bug data, scripts for
checking, etc), just write a post here on this thread (ping) to remind me. I can not find out this
data you need just now.
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))