It works!
Thanks
-Mikkel
Felix Radensky wrote:
Hi, Mikkel
You can try tg3 driver (available from 2.4.19 kernel).
It supports SysKonnect SK9dxx cards, as they are based
on Broadcom chip.
Felix.
Mikkel Christiansen wrote:
Hi
We're getting a kernel Oops when trying to use our SysKonnect cards.
The host has an ASUS A7M266-D motherboard and two SysKonnect SK9d21
cards. The kernel (2.4.17) was patched kernel with the patch from the
SysKonnect site, and booted with the sk9dlin drivers as loadable
modules.
Once booted the cards initializes ok - both to the cisco switch and to
another host (32bit pci) with 9d21 cards. Ping works fine as well.
However, whenever we try to establish a TCP connection - through ssh
or NPtcp - the kernel crashes with a kernel oops. Running ksymoops on
the oops message seems to indicate that the problem is with the
syskonnect driver (however, being new to kernel debugging, I'm not
really sure).
A trace of the TCP connection shows that the three way handshake is
fine - however suddenly the broken host stops ack'ing packets. And
after a while of receiving retransmissions from the other side it
decides to crash.
Any suggestions on solving this problem?
(I sent mail to syskonnect support yesterday, but haven't received
any reply)
-Mikkel
The following is the output from ksymoops - More details like kernel
config and boot log on: http://www.cs.auc.dk/~mixxel/sk9d21-oops
ksymoops 2.4.6 on i686 2.4.17ser-smp-sk. Options used
-v /pack/kernel/linux-ser-smp-sk/vmlinux (specified)
-k /proc/ksyms (specified)
-l /proc/modules (default)
-o /lib/modules/2.4.17ser-smp-sk/ (default)
-m /boot/System.map-2.4.17ser-smp-sk (specified)
cpu: 0, clocks: 2666974, slice: 1333487
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
rip login: Unable to handle kernel NULL pointer dereference at
virtual address 00000060
e081b837
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<e081b837>] Tainted: P
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000047 ebx: dfaf05a0 ecx: 0000000a edx: 00000043
esi: 00000000 edi: 0000002d ebp: dfaf8000 esp: c027bf0c
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, stackpage=c027b000)
Stack: dfb184c8 dfb18140 00000000 e0837000 dfb07010 dfb184b8 e081ba45
dfb18140
e0837000 00000000 00000000 dfd11cc0 04000001 00000000 0000000a
c01086d1
0000000a dfb18000 c027bf94 c02e2f00 c02b5a80 0000000a c027bf8c
c01088c6
Call Trace: [<e081ba45>] [<c01086d1>] [<c01088c6>] [<c01051d0>]
[<c01051d0>]
[<c010aa38>] [<c01051d0>] [<c01051d0>] [<c01051fc>] [<c0105272>]
[<c0105000>]
[<c0105043>]
Code: 83 7e 60 00 74 03 0f 0b 90 89 d0 03 86 84 00 00 00 89 86 84
>>EIP; e081b837 <[sk9dlin]ReceiveIrq+97/200> <=====
>>ebx; dfaf05a0 <_end+1f7dfafc/205085bc>
>>ebp; dfaf8000 <_end+1f7e755c/205085bc>
>>esp; c027bf0c <init_task_union+1f0c/2000>
Trace; e081ba45 <[sk9dlin]SkGiIsr+a5/200>
Trace; c01086d1 <handle_IRQ_event+51/80>
Trace; c01088c6 <do_IRQ+a6/f0>
Trace; c01051d0 <default_idle+0/40>
Trace; c01051d0 <default_idle+0/40>
Trace; c010aa38 <call_do_IRQ+5/d>
Trace; c01051d0 <default_idle+0/40>
Trace; c01051d0 <default_idle+0/40>
Trace; c01051fc <default_idle+2c/40>
Trace; c0105272 <cpu_idle+42/60>
Trace; c0105000 <_stext+0/0>
Trace; c0105043 <rest_init+43/50>
Code; e081b837 <[sk9dlin]ReceiveIrq+97/200>
00000000 <_EIP>:
Code; e081b837 <[sk9dlin]ReceiveIrq+97/200> <=====
0: 83 7e 60 00 cmpl $0x0,0x60(%esi) <=====
Code; e081b83b <[sk9dlin]ReceiveIrq+9b/200>
4: 74 03 je 9 <_EIP+0x9>
Code; e081b83d <[sk9dlin]ReceiveIrq+9d/200>
6: 0f 0b ud2a Code; e081b83f
<[sk9dlin]ReceiveIrq+9f/200>
8: 90 nop Code; e081b840
<[sk9dlin]ReceiveIrq+a0/200>
9: 89 d0 mov %edx,%eax
Code; e081b842 <[sk9dlin]ReceiveIrq+a2/200>
b: 03 86 84 00 00 00 add 0x84(%esi),%eax
Code; e081b848 <[sk9dlin]ReceiveIrq+a8/200>
11: 89 86 84 00 00 00 mov %eax,0x84(%esi)
<0>Kernel panic: Aiee, killing interrupt handler!
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
