|author||Linus Torvalds <firstname.lastname@example.org>||2006-11-17 19:31:09 -0800|
|committer||Linus Torvalds <email@example.com>||2006-11-17 19:31:09 -0800|
Revert "ACPI: created a dedicated workqueue for notify() execution"
This reverts commit 37605a6900f6b4d886d995751fcfeef88c4e462c. Again. This same bug has now been introduced twice: it was done earlier by commit b8d35192c55fb055792ff0641408eaaec7c88988, only to be reverted last time in commit 72945b2b90a5554975b8f72673ab7139d232a121. We must NOT try to queue up notify handlers to another thread than the normal ACPI execution thread, because the notifications on some systems seem to just keep on accumulating until we run out of memory and/or threads. Keeping events within the one deferred execution thread automatically throttles the events properly. At least the Compaq N620c will lock up completely on the first thermal event without this patch reverted. Cc: David Brownell <firstname.lastname@example.org> Cc: Len Brown <email@example.com> Cc: Alexey Starikovskiy <firstname.lastname@example.org> Signed-off-by: Linus Torvalds <email@example.com>
Diffstat (limited to 'CREDITS')
0 files changed, 0 insertions, 0 deletions