There is missing text here as well.
if (address < PAGE_SIZE)
printk(KERN_ALERT "Unable to handle kernel NULL pointer dereference");
else
printk(KERN_ALERT "Unable to handle kernel paging request");
printk(" at virtual address %08lx\n",address);
printk(" printing eip:\n");
> Feb 13 20:37:41 mesh kernel: printing eip:
> Feb 13 20:37:41 mesh kernel: c012e276
> Feb 13 20:37:41 mesh kernel: Oops: 0002
> Feb 13 20:37:41 mesh kernel: CPU: 0
> Feb 13 20:37:41 mesh kernel: EIP: 0060:[<c012e276>] Not tainted
> Feb 13 20:37:41 mesh kernel: EFLAGS: 00010046
> Feb 13 20:37:41 mesh kernel: EIP is at mod_timer+0x96/0x7e0
> Feb 13 20:37:41 mesh kernel: eax: 00000000 ebx: c0147440 ecx: 00000007 edx: 00001388
> Feb 13 20:37:41 mesh kernel: esi: 850fc085 edi: c06436c0 ebp: c11c7ed0 esp: c11c7ea0
> Feb 13 20:37:41 mesh kernel: ds: 007b es: 007b ss: 0068
> Feb 13 20:37:41 mesh kernel: Process pdflush (pid: 5, threadinfo=c11c6000 task=c113d980)
> Feb 13 20:37:41 mesh kernel: Stack: c11c7ec0 c0146229 c11c7f04 00000000 00000080 c0147320 c11c7ee4 00000000
> Feb 13 20:37:41 mesh kernel: 00000297 000733cf c11c7ee4 00000000 c11c7f90 c0147426 c06436c0 000733cf
> Feb 13 20:37:41 mesh kernel: 0006ab17 00000000 00000000 c11c7ee0 00000000 00000001 00000000 00000001
> Feb 13 20:37:41 mesh kernel: Call Trace:
> Feb 13 20:37:41 mesh kernel: [<c0146229>] __get_page_state+0x29/0x90
> Feb 13 20:37:41 mesh kernel: [<c0147320>] wb_kupdate+0x0/0x120
That is a statically stored timer. It would appear that some other timer
from some other random part of the kernel has got itself scribbled on.
Maybe networking?
-
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/