* OSM doesn't send notice on traps 129, 130 and 131
@ 2011-03-13 13:20 Yevgeny Kliteynik
[not found] ` <4D7CC496.1040805-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
0 siblings, 1 reply; 2+ messages in thread
From: Yevgeny Kliteynik @ 2011-03-13 13:20 UTC (permalink / raw)
To: alexne-VPRAkNaXOzVWk0Htik3J/w, elido-VPRAkNaXOzVWk0Htik3J/w,
hal-VPRAkNaXOzVWk0Htik3J/w
Cc: Linux RDMA, Yevgeny Kliteynik
It appears that SM is not sending notice on receiving traps 129, 130 and 131.
>From osm_trap_rcv.c:
547 /* If we reached here due to trap 129/130/131 - do not need to do
548 the notice report. Just goto exit. We know this is the case
549 if physp_change_trap is TRUE. */
550 if (physp_change_trap == TRUE)
551 goto Exit;
Does anybody knows why? Spec doesn't say that SM shouldn't send notice on these traps. Is this a bug?
-- YK
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 2+ messages in thread[parent not found: <4D7CC496.1040805-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>]
* RE: OSM doesn't send notice on traps 129, 130 and 131 [not found] ` <4D7CC496.1040805-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org> @ 2011-03-13 15:15 ` Hal Rosenstock 0 siblings, 0 replies; 2+ messages in thread From: Hal Rosenstock @ 2011-03-13 15:15 UTC (permalink / raw) To: kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org, Alex Netes, Eli Dorfman Cc: Linux RDMA This is a long standing IBA spec non conformance. I guess nobody to date has wanted to subscribe to those reports on hardware events (local link integrity threshold, excessive Buffer Overrun threshold, and flow control watchdog expired). -- Hal -----Original Message----- From: Yevgeny Kliteynik [mailto:kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org] Sent: Sunday, March 13, 2011 9:20 AM To: Alex Netes; Eli Dorfman; Hal Rosenstock Cc: Linux RDMA; Yevgeny Kliteynik Subject: OSM doesn't send notice on traps 129, 130 and 131 It appears that SM is not sending notice on receiving traps 129, 130 and 131. >From osm_trap_rcv.c: 547 /* If we reached here due to trap 129/130/131 - do not need to do 548 the notice report. Just goto exit. We know this is the case 549 if physp_change_trap is TRUE. */ 550 if (physp_change_trap == TRUE) 551 goto Exit; Does anybody knows why? Spec doesn't say that SM shouldn't send notice on these traps. Is this a bug? -- YK -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-03-13 15:15 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-03-13 13:20 OSM doesn't send notice on traps 129, 130 and 131 Yevgeny Kliteynik
[not found] ` <4D7CC496.1040805-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2011-03-13 15:15 ` Hal Rosenstock
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox