redonkable
/
alistair23-linux
1
0
Fork 0
Code Releases Activity

[PATCH] schedule_timeout(): improve warning message 

Kyle is hitting this warning, and we don't have a clue what it's caused by.
Add the obligatory dump_stack().

Cc: kyle <kylewong@southa.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
hifive-unleashed-5.1
Andrew Morton 2006-12-22 01:10:14 -08:00 committed by Linus Torvalds
parent fadfc8e930
commit 5b149bcc23
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
kernel/timer.c
View File

@ -1344,11 +1344,10 @@ fastcall signed long __sched schedule_timeout(signed long timeout)
* should never happens anyway). You just have the printk()
* that will tell you if something is gone wrong and where.
*/
if (timeout < 0)
{
if (timeout < 0) {
printk(KERN_ERR "schedule_timeout: wrong timeout "
"value %lx from %p\n", timeout,
__builtin_return_address(0));
"value %lx\n", timeout);
dump_stack();
current->state = TASK_RUNNING;
goto out;
}