sleeping function called from cpufreq

From: Pierre Ossman
Date: Mon Nov 07 2005 - 03:36:37 EST


As of lately I've been getting tonnes of these:

[ 610.185635] Debug: sleeping function called from invalid context at include/linux/rwsem.h:43
[ 610.185647] in_atomic():1, irqs_disabled():0
[ 610.185653] [<c01041be>] dump_stack+0x1e/0x20
[ 610.185667] [<c0119b62>] __might_sleep+0xa2/0xc0
[ 610.185678] [<c029de86>] cpufreq_notify_transition+0x46/0x220
[ 610.185690] [<e09d08fc>] centrino_target+0xfc/0x130 [speedstep_centrino]
[ 610.185708] [<c029f17f>] __cpufreq_driver_target+0x5f/0x70
[ 610.185718] [<c02a029d>] cpufreq_set+0x7d/0xa0
[ 610.185728] [<c02a0339>] store_speed+0x49/0x50
[ 610.185737] [<c029e6c6>] store+0x46/0x60
[ 610.185745] [<c01a5f27>] flush_write_buffer+0x37/0x40
[ 610.185754] [<c01a5f98>] sysfs_write_file+0x68/0x90
[ 610.185763] [<c01639b8>] vfs_write+0xa8/0x190
[ 610.185773] [<c0163b57>] sys_write+0x47/0x70
[ 610.185781] [<c01032bb>] sysenter_past_esp+0x54/0x75

Ideas on solving it?

Rgds
Pierre
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/