Date: Fri, 05 Dec 2014 14:00:41 +0000 From: Steven Hartland <killing@multiplay.co.uk> To: Borja Marcos <borjam@sarenet.es> Cc: freebsd-current@freebsd.org Subject: Re: Fix Emulex "oce" driver in CURRENT Message-ID: <5481BA89.5010201@multiplay.co.uk> In-Reply-To: <FF410A78-138C-412C-8CC1-40CADF4AF6CD@sarenet.es> 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> <FF410A78-138C-412C-8CC1-40CADF4AF6CD@sarenet.es>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/12/2014 13:07, Borja Marcos wrote: > On Dec 5, 2014, at 2:00 PM, Steven Hartland wrote: > >> On 04/09/2014 09:49, Borja Marcos wrote: >>> On Jun 30, 2014, at 8:02 PM, John Baldwin wrote: >>> >>>> 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, >>> >>> 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. >> 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. >> >> Did the commit of the additional locking never make it in? > Not as far as I know. I´ve updated a couple of machines here to 10-STABLE and I've been applying the patch manually myself. > > I don't think it's been applied even to -HEAD. > > 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. Thanks for the quick reply Borja, review of the patch is now up: /https://reviews.freebsd.org/D1269 Hopefully we can get this in the tree and make oce usable moving forward. Regards Steve /
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5481BA89.5010201>