[Kernel-packages] [Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10

2015-09-08 Thread Torsten Römer
With the freezes I had it was not possible to "revive" from, all I could do is long-press the power button. So maybe the freezes you encounter are another issue, maybe this bug: https://bugs.launchpad.net/kubuntu-ppa/+bug/1384512 It is about KDE but sounds similar and might be related to the vide

[Kernel-packages] [Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10

2015-09-07 Thread Xiaochuan Yu
My laptop freezes after idling over night at lockscreen. I have Lenovo y410p on Ubuntu 14.04. So far I've been able to "revive" it by going into tty (ctrl+alt+f2) and then do `unity start` which prints some some errors and then brings me to the lockscreen not frozen. The first time I login, scre

[Kernel-packages] [Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10

2014-12-09 Thread Torsten Römer
Following your experience, I have disabled "CPU Power Management" and "PCI Express Power Management" in the BIOS of my Lenovo L420. I did not have a single freeze in one month now (before about once a week), so I suppose this solved my freezing issues as well. The fact that the freezes occurred on

[Kernel-packages] [Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10

2014-11-10 Thread Přemysl Čermák
It seems, that problem has been solved when i try to disable CPU C states and extended C states in bios in my case. It's about one month without freeze. May be that it's relates to CPU C states VS power supply, which has problems with lowered power consumption or simly doesn't support this feature

[Kernel-packages] [Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10

2014-09-21 Thread Torsten Römer
I am not aware of any workaround and I wonder if our freezes are related or if we have individual hardware issues. But I am pretty sure I did not have theses issues before 13.10 on the same hardware. -- You received this bug notification because you are a member of Kernel Packages, which is subsc

[Kernel-packages] [Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10

2014-09-21 Thread Přemysl Čermák
Is there any workaround? It's little critical for my (Kubuntu 14.04) workstation, because i use it also for remote access thru SSH and computer is completely unreachable due this bug. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to

[Kernel-packages] [Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10

2014-07-20 Thread Torsten Römer
Unfortunately I still have this problem, by the time with kubuntu 14.04. Often when the system is idling for some hours, it eventually freezes. I again let Memtest86 running, it did 9 passes in more than 13 hours without error, so it is probably not a memory issue. There is usually an external sc

[Kernel-packages] [Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10

2013-12-08 Thread Torsten Römer
Thank you Joseph. After running about one week without the bad memory module and another week with a new 2nd 4GB module without any freeze I think we can assume this bug is invalid :-) Torsten -- You received this bug notification because you are a member of Kernel Packages, which is subscribed

[Kernel-packages] [Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10

2013-11-27 Thread Joseph Salisbury
I'll mark this as invalid for now, since it appears to be due to bad memory. Just change the status back to confirmed if you find the issue still happens after fixing the memory issue. ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Con

[Kernel-packages] [Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10

2013-11-27 Thread Torsten Römer
I have done a memory test as suggested in https://help.ubuntu.com/community/DebuggingSystemCrash - sorry for not reading it earlier. Errors were found at four addresses in the memory area of the second 4 GB module. After removing it and running with only the first 4 GB, no more errors were found.