[ofw] Access Violation while running ND test over winverb

Uri Habusha urih at mellanox.co.il
Thu Nov 4 09:48:10 PDT 2010


Hi we run ND test over winverb, in same time the port change its status from up to down and we got the following access violation. Is it a known issue? If so do we have a fix for it? If no is there is any chances that winverb owner will take look on it.

See attached file for more debug output

Thanks in advance
Uri

STACK_TEXT:
: Wdf01000!FxObjectHandleGetPtr+0x103
: Wdf01000!imp_WdfObjectAcquireLock+0x2a
: winverbs!WdfObjectAcquireLock+0x1b [d:\winddk\6001.18001\inc\wdf\kmdf\1.7\wdfsync.h @ 61]
: winverbs!WvDeviceCompleteRequests+0x1f [s:\builds\6627\branches\mlnx_winof-2_1_2\core\winverbs\kernel\wv_device.c @ 100]
: winverbs!WvDeviceEventHandler+0xba [s:\builds\6627\branches\mlnx_winof-2_1_2\core\winverbs\kernel\wv_device.c @ 141]
: mlx4_hca!ca_event_handler+0x103 [s:\builds\6627\branches\mlnx_winof-2_1_2\hw\mlx4\kernel\hca\data.c @ 133]
: mlx4_hca!event_handler+0x21 [s:\builds\6627\branches\mlnx_winof-2_1_2\hw\mlx4\kernel\hca\data.c @ 148]
: mlx4_bus!ib_dispatch_event+0x77 [s:\builds\6627\branches\mlnx_winof-2_1_2\hw\mlx4\kernel\bus\core\device.c @ 559]
: mlx4_bus!mlx4_ib_event+0x7f [s:\builds\6627\branches\mlnx_winof-2_1_2\hw\mlx4\kernel\bus\ib\main.c @ 669]
: mlx4_bus!mlx4_dispatch_event+0xa7 [s:\builds\6627\branches\mlnx_winof-2_1_2\hw\mlx4\kernel\bus\net\intf.c @ 138]
: mlx4_bus!mlx4_eq_int+0x190 [s:\builds\6627\branches\mlnx_winof-2_1_2\hw\mlx4\kernel\bus\net\eq.c @ 144]
: mlx4_bus!mlx4_dpc_msix+0x34 [s:\builds\6627\branches\mlnx_winof-2_1_2\hw\mlx4\kernel\bus\net\eq.c @ 284]
: nt!KiRetireDpcList+0x117
: nt!KiIdleLoop+0x62
: nt!zzz_AsmCodeRange_End+0x4
: 0xfffff800

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofw/attachments/20101104/136c8ebf/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: vinverbs.txt
URL: <http://lists.openfabrics.org/pipermail/ofw/attachments/20101104/136c8ebf/attachment.txt>


More information about the ofw mailing list