Hello,
I'm debugging a new synchronous card driver, and even though the driver
seems stable, sometimes I get kernel oopsen like the one below when doing
an FTP reception transfer:
Unable to handle kernel paging request at virtual address c4834824
current->tss.cr3 = 00101000, %cr3 = 00101000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c4834824>]
EFLAGS: 00010292
eax: 00000009 ebx: 00000002 ecx: 00000001 edx: c281908c
esi: c2819070 edi: 00000001 ebp: c289e048 esp: c01dff1c
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, process nr: 0, stackpage=c01df000)
Stack: f1e85200 83fffb77 c8e904c4 90000000 28244c8b 8308798b 387501ff
448b016a
e8504424 fffb8264 4824748b f008c483 187eab0f c085c019 016a1a75
76bee856
c483fffb 287e8308 56097402 fb76efe8 04c483ff 4024548b 0974d285
7796e852
Call Trace:
Code:
The weird thing about it is that there is no call trace nor code to be
used in the ksymoops. If I try to use all I got in ksymoops (i.e., the
output shown above), it doesn't return anything, i.e., it stays there
waiting for actually useful data to come in.
Is there any way to figure out what is causing this kernel oops !?!?
Without the call trace / code, it's useless to me, so if somebody could
shed some light on it for me, I'd really appreciate it.
If you need more info (e.g., /proc/ksyms, System.map, etc.), please let me
know in PVT.
TIA and Regards,
Ivan
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
