Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 5 Dec 2014 14:07:13 +0100
From:      Borja Marcos <borjam@sarenet.es>
To:        Steven Hartland <killing@multiplay.co.uk>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Fix Emulex "oce" driver in CURRENT
Message-ID:  <FF410A78-138C-412C-8CC1-40CADF4AF6CD@sarenet.es>
In-Reply-To: <5481AC78.6050107@multiplay.co.uk>
References:  <CAO0mX5aGStHevUa=Hyk4gru5f4mwczW=6%2B9jbJtMYC1i12QF7w@mail.gmail.com> <201406301402.42119.jhb@freebsd.org> <8BA1A243-8EA9-449A-A2D2-4E03487CE3E0@sarenet.es> <5481AC78.6050107@multiplay.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help

On Dec 5, 2014, at 2:00 PM, Steven Hartland wrote:

>=20
> On 04/09/2014 09:49, Borja Marcos wrote:
>> On Jun 30, 2014, at 8:02 PM, John Baldwin wrote:
>>=20
>>> I think these sound fine, but I've cc'd Xin Li (delphij@) who has =
worked with
>>> folks at Emulex to maintain this driver.  He is probably the best =
person to
>>> review this.
>> Hi,
>>=20
>> Seems 10.1 is on the pipeline now, but as far as I know none of these =
fixes have been applied to -STABLE. Any chances to do it yet? As far as =
I know, the "oce" driver is currently unusable in -STABLE. I managed to =
cause a panic reliably within 30 seconds.
>=20
> Was there any conclusion to this, current and releng/10.0 & =
releng/10.1 seem pretty similar with regards oce but a customer is =
reporting panics very similar to this thread.
>=20
> Did the commit of the additional locking never make it in?

Not as far as I know. I=B4ve updated a couple of machines here to =
10-STABLE and I've been applying the patch manually myself.=20

I don't think it's been applied even to -HEAD.=20

For now I've told my coworkers to avoid Emulex cards whenever possible. =
As far as  I know the driver is unusable in its present state.






Borja.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FF410A78-138C-412C-8CC1-40CADF4AF6CD>