I'm getting really nervous :-( Is kdb able to track who caused unbalanced
in_atomic() incrementation?
After more than week of stable system I run simple
"arp vanicka.vc.cvut.cz" few minutes ago, and after arp output I got
sleeping function called from illegal context, quickly followed by two
scheduling while atomic, and finally it died because of userspace faults
when in_atomic() is != 0 are treated as kernel ones...
As I saw nobody else reporting this or simillar problem, I'll start
looking at e100 driver I use. Maybe it did not occured because of I
was running -acX kernels since 25th Oct until yesterday. Anybody knows?
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
Debug: sleeping function called from illegal context at include/asm/semaphore.h:119
Call Trace:
[..........] __might_sleep+0x43/0x47
[..........] seq_read
........... vfs_read
........... sys_read
[..........] syscall_call+0x7/0xb
bad: scheduling while atomic!
[..........] schedule
............ sys_read
[..........] work_resched
bad: scheduling while atomic!
[..........] schedule
............ sys_munmap
[..........] work_resched
Unable to handle kernel paging request...
...
EIP: 0x4004DB65
...
Process: arp
-
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/