> I managed to get a trace of the program together with an oops,
> the same one that was in kernel 2.2.9.
> I hope you can find time to take a look at it.
Okay. The trace contains this:
socket(PF_AX25, SOCK_SEQPACKET, 0) = 7
bind(7, {sa_family=3, sa_data="\240\202h\250\252@\0\367\377\277\1\0\0\0"}, 72) = 0
ioctl(7, FIONBIO, [1]) = 0
connect(7, {sa_family=3, sa_data="\240\222b\244\234\222\0\363\v\10\0\0\0\0"}, 72) = -1 EINPROGRESS (Operation now in progress)
[...]
ioctl(7, FIONBIO, [0]) = 0
[...]
write(7, "nodes\r", 6) = 6
[...]
read(7, <unfinished ...>
+++ killed by SIGSEGV +++
..which points to AX25, but I expect you already knew that.
> Right after the oops, I now get these messages on my screen:
> 'packet sk destroy delayed'.
> The trace is attached to my mail as a gzipped file.
> Let me know if you need to know more....
> ------------------------------------------------------------------
> Jun 15 20:31:56 pa4tu kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000004
> Jun 15 20:31:56 pa4tu kernel: current->tss.cr3 = 00419000, %cr3 = 00419000
> Jun 15 20:31:56 pa4tu kernel: *pde = 00000000
> Jun 15 20:31:56 pa4tu kernel: Oops: 0002
> Jun 15 20:31:56 pa4tu kernel: CPU: 0
> Jun 15 20:31:56 pa4tu kernel: EIP: 0010:[skb_recv_datagram+343/400]
> Jun 15 20:31:56 pa4tu kernel: EFLAGS: 00010047
> Jun 15 20:31:56 pa4tu kernel: eax: c02d64e0 ebx: c0548064 ecx: 00000256 edx: 00000000
> Jun 15 20:31:56 pa4tu kernel: esi: 00000100 edi: c0548020 ebp: c0548064 esp: c083fe84
> Jun 15 20:31:56 pa4tu kernel: ds: 0018 es: 0018 ss: 0018
> Jun 15 20:31:56 pa4tu kernel: Process tnt (pid: 225, process nr: 21, stackpage=c083f000)
> Jun 15 20:31:56 pa4tu kernel: Stack: c100adfc c083ff80 c083fea8 c0548064 c05e108c bffff448 c100ae49 c0548020
> Jun 15 20:31:56 pa4tu kernel: 00000000 00000000 c083fec8 c06055dc 00000100 c100adfc c083ff80 c083feec
> Jun 15 20:31:56 pa4tu kernel: c0548020 c10207c0 c101fe40 00000000 c10207c0 00000001 bffffa38 bffff55c
> Jun 15 20:31:57 pa4tu kernel: Call Trace: [3c509:el3_probe+-94804/5532] [3c509:el3_probe+-94727/5532] [3c509:el3_probe+-94804/5532] [3c509:el3_probe+-6288/5532] [3c509:el3_probe+-8720/5532] [3c509:el3_probe+-6288/5532] [3c509:el3_probe+-22159/5532]
> Jun 15 20:31:57 pa4tu kernel: [send_sig_info+363/672] [notify_parent+184/196] [sock_recvmsg+65/180] [3c509:el3_probe+-94804/5532] [sock_read+133/148] [sys_read+166/188] [tracesys+24/38] [startup_32+43/286]
> Jun 15 20:31:57 pa4tu kernel: Code: 89 5a 04 89 13 c7 00 00 00 00 00 c7 40 04 00 00 00 00 c7 40
> Jun 15 20:31:57 pa4tu kernel: packet sk destroy delayed
> Jun 15 20:32:27 pa4tu last message repeated 3 times
> ----------------------------------------------------------------------
The addresses here look wrong. Is ax25 a module? If so, I'd look up the
symbols by hand in 'sort /proc/ksyms | less', to make sure we know what
we're looking at.
el3_probe+-94804/5532 doesn't make any sense. I'm not up to speed on
klogd really -- can it decode oopses from modules?
Tim.
*/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/