Re: random and persistant hard kernel lock, 10.10 (old and newer kernel) and 12.04 (l
Then I guess it would be the ACPI cpufreq driver. The dmesg you provided is indicating that it's not nForce2 (it could have made an error!).
Originally Posted by dave.kts
This would give a very strong indication that you are using the generic driver which uses ACPI. That certainly makes some alarmbells ring since ACPI is known for it's diverse amount of 'implementations'.
Yes, I really think you should test with cpufreq disabled inside your BIOS. Test it for 2 or 3 weeks, if the hangs are gone then we could look at bisecting it. Or I could give you steps to disable cpufreq using kernel compilation. This would allow you to use cpufreq under Windows, while avoiding it under Linux. That would be a suitable workaround.
Even better would be to start bisecting, I looked at the amount of commits that were made to the acpi cpufreq driver between .35 and .36, there were only ten. Assuming that the occurence of you switching cpufreq driver between .35 and .36 has not occurred. And assuming that .36 allowed you to use cpufreq for this first time has not occurred.
linux-git/fs/super.c: "Self-destruct in 5 seconds. Have a nice day...\n",