https://bugzilla.novell.com/show_bug.cgi?id=299891#c62
--- Comment #62 from Thomas Renninger 2007-09-26 10:11:54 MST ---
I tried:
- MUTEX_DEBUG, PROVE_LOCKING configs
- I also tried to 100% reproduce this with some delays, no luck until now
It's probably hanging at:
lock_policy_rwsem_write(cpu);
in
cpufreq_add_dev(..) in drivers/cpufreq/cpufreq.c
But this lock is clustered all over the cpufreq core, I even couldn't reproduce
this at all anymore.
We can either remove CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND and set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y again.
We would loose the ability that cpufreq is set up at installation time then
Or people need to add brokenmodules=powernow-k8 to install on affected machines
and CPUFREQ=off later until this is finally tracked down.
Jogchum: I won't have time at around 19:00, maybe later, you may want to ping
me through mail or icq.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.