[ofw] Access Violation while running ND test over winverb

Uri Habusha urih at mellanox.co.il
Sun Nov 7 01:24:23 PST 2010


Following is some information I take from the debugger. Hopefully it will help. 

Please let me know if mini dump will help.

Uri

WvDeviceEventHandler()

4: kd> ??pEvent
struct _ib_event_rec * 0xfffffa60`01c5baf0
   +0x000 context          : 0xfffffa80`16f41170 
   +0x000 context_padding  : 0xfffffa80`16f41170
   +0x008 type             : 16 ( IB_AE_PORT_DOWN )
   +0x010 vendor_specific  : 0x20206f49
   +0x018 port_number      : 0x2 ''

mlx4_hca!ca_event_handler

4: kd> ??ev
struct ib_event * 0xfffffa60`01c5bbd0
   +0x000 device           : 0xfffffa80`1056a520 ib_device
   +0x008 element          : <unnamed-tag>
   +0x010 event            : 16 ( IB_EVENT_PORT_ERR )
   +0x018 x                : ib_event_ex
4: kd> ??ev->element
union <unnamed-tag>
   +0x000 cq               : 0xfffffa80`0aac7002 ib_cq
   +0x000 qp               : 0xfffffa80`0aac7002 ib_qp
   +0x000 srq              : 0xfffffa80`0aac7002 ib_srq
   +0x000 port_num         : 0x2 ''
4: kd> ??ev->element.cq
struct ib_cq * 0xfffffa80`0aac7002
   +0x000 device           : 0xe3a80000`0000f1b3 ib_device
   +0x008 p_uctx           : 0x0001ffff`fa800e58 ib_ucontext
   +0x010 comp_handler     : 0x25260000`00000000     void  +2526000000000000
   +0x018 event_handler    : 0x00020000`00020007     void  +2000000020007
   +0x020 cq_context       : 0x00080000`00000000 
   +0x028 cqe              : 524288
   +0x02c usecnt           : 0
4: kd> ??ev->element.qp
struct ib_qp * 0xfffffa80`0aac7002
   +0x000 device           : 0xe3a80000`0000f1b3 ib_device
   +0x008 pd               : 0x0001ffff`fa800e58 ib_pd
   +0x010 send_cq          : 0x25260000`00000000 ib_cq
   +0x018 recv_cq          : 0x00020000`00020007 ib_cq
   +0x020 srq              : 0x00080000`00000000 ib_srq
   +0x028 p_uctx           : 0x00000000`00080000 ib_ucontext
   +0x030 event_handler    : 0x00050000`00050000     void  +5000000050000
   +0x038 qp_context       : (null) 
   +0x040 qp_num           : 0
   +0x044 qp_type          : 0x57110000 (No matching name)
4: kd> ??ev->element.srq
struct ib_srq * 0xfffffa80`0aac7002
   +0x000 device           : 0xe3a80000`0000f1b3 ib_device
   +0x008 pd               : 0x0001ffff`fa800e58 ib_pd
   +0x010 p_uctx           : 0x25260000`00000000 ib_ucontext
   +0x018 event_handler    : 0x00020000`00020007     void  +2000000020007
   +0x020 srq_context      : 0x00080000`00000000 
   +0x028 usecnt           : 524288
4: kd> ??pEvent
struct _ib_event_rec * 0xfffffa60`01c5baf0
   +0x000 context          : 0xfffffa80`16f41170 
   +0x000 context_padding  : 0xfffffa80`16f41170
   +0x008 type             : 16 ( IB_AE_PORT_DOWN )
   +0x010 vendor_specific  : 0x20206f49
   +0x018 port_number      : 0x2 ''

-----Original Message-----
From: Hefty, Sean [mailto:sean.hefty at intel.com] 
Sent: Thursday, November 04, 2010 9:18 PM
To: Uri Habusha; ofw at lists.openfabrics.org; Smith, Stan
Subject: RE: Access Violation while running ND test over winverb

> Thanks. Please let me know if you need more information from the debugger

In the event that's reported, what is the value of port_number?

This would be pEvent->port_number in WvDeviceEventHandler(), or ev->element.port_num in ca_event_handler().

- Sean



More information about the ofw mailing list