[openib-general] SDP: still getting sk_alloc() panic, any ideas?

[Tom Duffy]

I am still getting the panic when you try to connect to a machine and
it is not listening (but has ib_sdp loaded):

[root at sins-stinger-10 ~]# ----------- [cut here ] --------- [please
bite here ] ---------
Kernel BUG at "/build1/tduffy/openib-work/linux-2.6.12-openib/in:352
invalid operand: 0000 [1] SMP
CPU 1
Modules linked in: ib_sdp kdapltest ib_dat_provider dat ib_at ib_cm
md5 ipv6 parport_pc lp parport autofs4 nfs lockd rfcomm l2cap
bluetooth pcmcia yenta_socket rsrc_nonstatic pcmcia_core sunrpc ext3
jbd dm_mod video container button battery ac ohci_hcd tpm_atmel tpm
i2c_amd756 i2c_core shpchp ib_mthca ib_ipoib ib_sa ib_mad ib_core tg3
floppy xfs exportfs mptscsih mptbase sd_mod scsi_mod
Pid: 3683, comm: ib_cm/1 Not tainted 2.6.12openib
RIP: 0010:[<ffffffff802dd6b9>] <ffffffff802dd6b9>{sk_alloc+297}
RSP: 0018:ffff81003c7bdc68  EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff8100668bf750 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 000000000000001b RDI: ffffffff8834f200
RBP: ffffffff8834ee00 R08: 0000000000000000 R09: ffff8100668bf750
R10: 0000000000000000 R11: 0000000000000001 R12: ffffffff8834e680
R13: 00000000000000d0 R14: 0000000000000001 R15: 000000000000001b
FS:  00002aaaaaf01d00(0000) GS:ffffffff804e7000(0000) knlGS:0000000055587260
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 00007fffffd9815c CR3: 000000007cade000 CR4: 00000000000006e0
Process ib_cm/1 (pid: 3683, threadinfo ffff81003c7bc000, task ffff8100416a8720)
Stack: ffff81007e24d910 ffff81006f2f9c58 0000000100000001 ffff810037d81aec
       0000000000000000 ffff81005132e330 ffff81000adf52d8 ffff81005132e330
       ffff81005132e388 ffffffff8833dc93
Call Trace:<ffffffff8833dc93>{:ib_sdp:sdp_conn_alloc+35}
<ffffffff88344a0f>{:ib_sdp:sdp_cm_req_handler+2111}
       <ffffffff80166508>{check_spinlock_acquired+24}
<ffffffff88343d5f>{:ib_sdp:sdp_cm_event_handler+175}
       <ffffffff882ee3d2>{:ib_cm:cm_process_work+50}
<ffffffff882efba9>{:ib_cm:cm_work_handler+1881}
       <ffffffff882ef450>{:ib_cm:cm_work_handler+0}
<ffffffff8014906c>{worker_thread+476}
       <ffffffff80132710>{default_wake_function+0}
<ffffffff8014d720>{keventd_create_kthread+0}
       <ffffffff80148e90>{worker_thread+0}
<ffffffff8014d720>{keventd_create_kthread+0}
       <ffffffff8014d9a9>{kthread+217} <ffffffff80133c60>{schedule_tail+64}
       <ffffffff8010f6db>{child_rip+8}
<ffffffff8014d720>{keventd_create_kthread+0}
       <ffffffff8011d5f0>{flat_send_IPI_mask+0} <ffffffff8014d8d0>{kthread+0}
       <ffffffff8010f6d3>{child_rip+0}

Code: 0f 0b b8 03 37 80 ff ff ff ff 60 01 65 8b 04 25 34 00 00 00
RIP <ffffffff802dd6b9>{sk_alloc+297} RSP <ffff81003c7bdc68>

Message from syslogd at sins-stinger-10 at Thu Jun 23 11:53:12 2005 ...
sins-stinger-10 kernel: invalid operand: 0000 [1] SMP

Any idea about this?

-tduffy