Hello Hal,
normally the timeout is set to 30 seconds. If you need more information about the "activation" please see [1].
[1]: http://openib.org/pipermail/openib-general/2005-October/012355.html
Mit freundlichen Gruessen / Kind Regards
Heiko Joerg Schick
IBM Deutschland Entwicklung GmbH
I/Ox Microcode Development
Linux Infiniband Device Drivers
Schoenaicher Str. 220
71032 Boeblingen
E-Mail: [EMAIL PROTECTED]
External: 49-7031-16-0 x4219, t/l: 120-4219
| Hal Rosenstock <[EMAIL PROTECTED]>
11.10.2005 14:48 |
|
Hi Heiko,
On Tue, 2005-10-11 at 08:43, Heiko J Schick wrote:
> this morning I've looked in detail into the problem you've reported on Oct
> 10 via the OpenIB mailing-list [1]. It seems that the kernel panic is an
> IPoIB issues.
>
> [1]: http://openib.org/pipermail/openib-general/2005-October/012353.html
>
> The following things appens:
>
> 1. modprobe hcad_mod ehca_nr_ports=1
> The eHCA InfiniBand Device Driver is loaded.
>
> 2. modprobe ib_mad
> The ib_mad stack creates an AQP1. This will start the port
> activation process.
> By my count it will take more than 110 / 120 seconds to activate a
> port.
> Our device driver gets a timeout, which means that the port is NOT
> active. and
> ib_modify_qp will not work (for any QP, doesn't matter if it was
> created in the ib_mad
> stack or in the ib_ipoib stack).
Where does this time to activate a port come from ? Is there some
maximum time in which the eHCA firmware requires this to be completed ?
-- Hal
_______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
