Messages in this thread | | | Date | Tue, 13 Jul 2004 14:07:56 +0300 | From | Lenar Lõhmus <> | Subject | Re: Preempt Threshold Measurements |
| |
With all those little patches added and 2.6.8-rc1-ck5 I got this in my dmesg (preempt=0 voluntary=1 if it makes difference):
bad: ld(3362) scheduling while atomic (1)! [<c02797ff>] schedule+0x43f/0x480 [<c01161a3>] kmap_atomic+0x13/0x70 [<c0117b5b>] __touch_preempt_timing+0xb/0x30 [<c0146ef7>] shmem_file_write+0x2f7/0x320 [<c014d890>] vfs_write+0xb0/0x100 [<c014d978>] sys_write+0x38/0x60 [<c0103ee1>] sysenter_past_esp+0x52/0x71 bad: krootimage(3483) scheduling while atomic (1)! [<c02797ff>] schedule+0x43f/0x480 [<c01161a3>] kmap_atomic+0x13/0x70 [<c0117b5b>] __touch_preempt_timing+0xb/0x30 [<c0146ef7>] shmem_file_write+0x2f7/0x320 [<c014d890>] vfs_write+0xb0/0x100 [<c014d978>] sys_write+0x38/0x60 [<c0103ee1>] sysenter_past_esp+0x52/0x71
Lenar
William Lee Irwin III wrote:
>That's not quite right. Amazing it didn't catch might_sleep() warnings. > > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |