[openib-general] ib_mthca "NOP command failed to generate interrupt (IRQ 169), aborting."

Don.Albert at Bull.com Don.Albert at Bull.com
Thu Mar 16 10:59:15 PST 2006


Michael and Roland,

This problem was resolved by updating the firmware.   See below:

> > Roland Dreier <rdreier at cisco.com> wrote on 03/14/2006 10:11:26 AM:
> > 
> > >  > >  - Try passing the option "fw_cmd_doorbell=0" when loading 
ib_mthca.
> > >  > >    Again, it shouldn't matter but maybe it does.
> > >  >
> > >  > I tried passing the option first, since it was the simplest 
> and quickest
> > >  > thing to try.  It worked.   The module now loads successfully.
> > >
> > > Hmm, that's interesting.  I wonder why that caused problems with the
> > > NOP command interrupt test.
> > >
> > > Michael, the situation here is that Arbel with FW 4.6.0 (I know it's
> > > old) fails with the latest mthca because the NOP test doesn't 
generate
> > > an event.  However, disabling fw_cmd_doorbell makes it work again.
> > > Do you know if this is a FW issue?
> > >
> > > Don, it would be nice if you could try a newer firmware to see if 
that
> > > works without the fw_cmd_doorbell option.
> > >
> > >  - R.

I copied over the firmware and the tvflash utility from our other system 
that
has the same type HCA card and flashed the new version (4.7.400) of the 
firmware.
After rebooting the system, the mthca driver nows loads successfully 
without
using the option "fw_cmd_doorbell=0" on the modprobe.  Apparently it was a 
problem
with the old firmware.

Thanks for the suggestions.

-Don Albert-
Bull HN Information Systems
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/general/attachments/20060316/5b14690a/attachment.html>


More information about the general mailing list