Closed GoogleCodeExporter closed 9 years ago
What steps will reproduce the problem? 1.r9623, nonvga_debug/x86 2.abnormal behavior: Starting shell [tish] at device [uart] root@embox:/#renice 1 0 root@embox:/#top PID USER PR COMMAND 0 0 1 kernel 1 0 1 top root@embox:/#renice 0 0 (WAITING) ---------------------------- or so: Starting shell [tish] at device [uart] root@embox:/# root@embox:/# root@embox:/#renice 1 0 root@embox:/#renice 1 0 ASSERTION FAILED at src/kernel/task/multi.c : 203, in function task_exit: critical_allows(CRITICAL_SCHED_LOCK) kernel debug panic Backtrace: sp pc func + offset -------- -------- -------------------------- 8 00697ec8 001a110d <__assertion_handle_failure+0x73> 7 00697f08 001411ab <task_exit+0x3c> 6 00697f58 00141351 <task_set_priority+0x0> 5 00697f88 00110344 <thread_trampoline+0x85> 4 00697fb8 00000000 3 00697ea8 00000085 2 00000085 53f000ff <sqrtl+0x53d51f7a> QEMU: Terminated
Original issue reported on code.google.com by ki.stfu on 20 Apr 2013 at 1:50
ki.stfu
second bug fixed by r9624
Original comment by ki.stfu on 20 Apr 2013 at 2:01
fixed by r9630
Original comment by ki.stfu on 20 Apr 2013 at 3:23
Original issue reported on code.google.com by
ki.stfu
on 20 Apr 2013 at 1:50