This is about the dead locks happening since cancel_delayed_work_sync()
got added to the ondemand/conservative governors.
I truncated a bit the CC list to most important people and mailing lists.
The patch is intended for 2.6.30 stable, but both patches together did
not get tested yet. If
Comment from Venkatesh:
...
This mutex is just serializing the changes to those variables. I could't
think of any functionality issues of not having the lock as such.
- rip it out.
CC: Venkatesh Pallipadi venkatesh.pallip...@intel.com
Signed-off-by: Thomas Renninger tr...@suse.de
---
From: Mathieu Desnoyers mathieu.desnoy...@polymtl.ca
Missed a call site for CPUFREQ_GOV_STOP to remove the rwlock taken around the
teardown. To make a long story short, the rwlock write-lock causes a circular
dependency with cancel_delayed_work_sync(), because the timer handler takes the
write
On Thursday 25 June 2009 16:01:23 Thomas Renninger wrote:
...
Arggh. I mixed up ker...@stable.org with sta...@kernel.org.
I bounced them there, please correct the address if you answer...
Thomas
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a
* Thomas Renninger (tr...@suse.de) wrote:
Comment from Venkatesh:
...
This mutex is just serializing the changes to those variables. I could't
think of any functionality issues of not having the lock as such.
- rip it out.
CC: Venkatesh Pallipadi venkatesh.pallip...@intel.com
The synaptics touchpad on my EeePC 701 dies on hibernation. 2.6.30 was
fine, and it doesn't happen on suspend to ram either. There are no
obvious error messages, but maybe this boot message is relevant:
Platform driver 'i8042' needs updating, please use dev_pm_ops
Alan
--
To unsubscribe from
-Original Message-
From: Mathieu Desnoyers [mailto:mathieu.desnoy...@polymtl.ca]
Sent: Thursday, June 25, 2009 7:26 AM
To: Thomas Renninger
Cc: ker...@stable.org; cpuf...@vger.kernel.org;
linux-ker...@vger.kernel.org; mi...@elte.hu; r...@sisk.pl;
hidave.darks...@gmail.com;
The bug is still present in v2.6.31-rc1
Cheers,
Jan
Rafael J. Wysocki r...@sisk.pl writes:
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.29. Please verify if it
2009/6/25 Alan Jenkins alan-jenk...@tuffmail.co.uk:
The synaptics touchpad on my EeePC 701 dies on hibernation. 2.6.30 was
fine, and it doesn't happen on suspend to ram either. There are no
obvious error messages, but maybe this boot message is relevant:
Platform driver 'i8042' needs
From: Mathieu Desnoyers mathieu.desnoy...@polymtl.ca
commit 42a06f2166f2f6f7bf04f32b4e823eacdceafdc9
Missed a call site for CPUFREQ_GOV_STOP to remove the rwlock taken around the
teardown. To make a long story short, the rwlock write-lock causes a circular
dependency with
Commit b253d2b2d28ead6fed012feb54694b3d0562839a although it was very
much needed to cleanup ondemand timer cleanly, openup a can of worms
related to locking dependencies in cpufreq.
Patch here defines the need for dbs_mutex and cleans up its usage in
conservative governor. This also resolves the
Commit b14893a62c73af0eca414cfed505b8c09efc613c although it was very
much needed to cleanup ondemand timer cleanly, openup a can of worms
related to locking dependencies in cpufreq.
Patch here defines the need for dbs_mutex and cleans up its usage in
ondemand governor. This also resolves the
Since recent chanegs to ondemand and conservative governor, there have been
multiple reports of lockdep issues in cpufreq. Patch series takes care of
these problems.
--
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to
* venkatesh.pallip...@intel.com (venkatesh.pallip...@intel.com) wrote:
Commit b14893a62c73af0eca414cfed505b8c09efc613c although it was very
much needed to cleanup ondemand timer cleanly, openup a can of worms
related to locking dependencies in cpufreq.
Patch here defines the need for
On Thu, 2009-06-25 at 12:46 -0700, Mathieu Desnoyers wrote:
* venkatesh.pallip...@intel.com (venkatesh.pallip...@intel.com) wrote:
Commit b14893a62c73af0eca414cfed505b8c09efc613c although it was very
much needed to cleanup ondemand timer cleanly, openup a can of worms
related to locking
* Pallipadi, Venkatesh (venkatesh.pallip...@intel.com) wrote:
On Thu, 2009-06-25 at 12:46 -0700, Mathieu Desnoyers wrote:
* venkatesh.pallip...@intel.com (venkatesh.pallip...@intel.com) wrote:
Commit b14893a62c73af0eca414cfed505b8c09efc613c although it was very
much needed to cleanup
On Thursday 25 June 2009 04:25:52 pm Mathieu Desnoyers wrote:
* Thomas Renninger (tr...@suse.de) wrote:
Comment from Venkatesh:
...
This mutex is just serializing the changes to those variables. I could't
think of any functionality issues of not having the lock as such.
- rip it out.
On Friday 26 June 2009 12:17:09 am Thomas Renninger wrote:
On Thursday 25 June 2009 04:25:52 pm Mathieu Desnoyers wrote:
* Thomas Renninger (tr...@suse.de) wrote:
Comment from Venkatesh:
...
This mutex is just serializing the changes to those variables. I
could't think of any
I'm running 2.6.28-rc2-mm1, the latest mm tree. I'd like to patch it
so it's up to date, and try using the daily snapshots.
Can somebody please tell me the steps to do this? I've diligently read
The Kernel Tester's Guide and done many google searches, and I've
got quilt, but I can't tell how
Charles 'Mack' Rhinelander wrote:
I'm running 2.6.28-rc2-mm1, the latest mm tree. I'd like to patch it
so it's up to date, and try using the daily snapshots.
Daily snapshots of what? mm-tree doesn't have daily snapshots.
Andrew Morton hasn't released a -mm patchset lately. He's been making
20 matches
Mail list logo
