On 04/04/2020 21.22, Dave Howorth wrote:
On Sat, 4 Apr 2020 20:26:10 +0200 "Carlos E. R."
wrote: On 04/04/2020 18.25, Dave Howorth wrote:
On Sat, 4 Apr 2020 17:11:59 +0200 "Carlos E. R." <> wrote:
On 04/04/2020 16.29, Patrick Shanahan wrote:
* Carlos E. R. <> [04-04-20 09:54]:
On 04/04/2020 15.32, Dave Howorth wrote: > On Sat, 04 Apr 2020 14:58:01 +0200 Per Jessen <> wrote: >> Carlos E.R. wrote:
> It could be that the 24hrs is irrelevant and the only thing that > matters is the hibernation cycle (plus maybe hardware > dependency). Carlos could test that quickly.
How?
:) hybernate and bring it back
That is known, in my system, to cause the problem. But without applying some change it proves nothing.
Then why did you previously say:
Here it takes a day, and after one hibernation/restore cycle. And may be related to the specific hardware.
To which Per replied:
Sure, like I said, "for what it's worth". I'll wait 24hours and report back. That it takes a day before the problem manifests itself does seem indicative of something not being cleaned up.
Which given what you've now said does mean Per was wasting his time and that my comment was useful, as Patrick saw.
I'm sorry, but I don't understand what you are trying to say.
You are proposing me to hibernate to cause the fault, but I already know that hibernating causes the fault. What do I gain by hibernating? What new knowledge? :-?
No, I'm not proposing anything, now. I was indeed proposing that you hibernate your machine, to save Per some time, but that was before you told us that you already knew that as a result of my proposal.
Now I'm just annoyed that you still haven't realized what on earth you had failed to do, and haven't apologized as a consequence. But I can't force you to realize and thus don't expect an apology.
I'm sorry, but I don't understand at all what you asked me to do. I can apologize, but I don't know for what! So, could you please explain what exactly did you people wanted me to do? Just hibernate? I have hibernated many times. :-? I have known for long, and I have said so several times, that the machine shows the problem after restoring from hibernation. Here, for example: Thread: "Everything is coredumping :-/"
The sequence of events is:
I reboot. Everything seems ok
I hibernate for the night.
On restore next morning (I see the kernel complaining about something), then after an hour I have problems. First thing I notice is either gkrellm crashed, or firefox fails to open links clicked on email. Sometimes the tab crashes; restore tab sometimes works, sometimes not. Things like starting a java process fail with some message about not being able to start a thread, resource temporarily unavailable. Which is absurd, this machine has 32 GB of ram and is barely loaded, just desktop stuff. 22 gigs free. Finally, I'm forced to reboot.
All this started after the updates in April 1, some of which I have reverted (glibc, kernel).
-- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)