Date: Fri, 05 Dec 2014 13:00:40 +0000 From: Steven Hartland <killing@multiplay.co.uk> To: freebsd-current@freebsd.org Subject: Re: Fix Emulex "oce" driver in CURRENT Message-ID: <5481AC78.6050107@multiplay.co.uk> In-Reply-To: <8BA1A243-8EA9-449A-A2D2-4E03487CE3E0@sarenet.es> References: <CAO0mX5aGStHevUa=Hyk4gru5f4mwczW=6%2B9jbJtMYC1i12QF7w@mail.gmail.com> <201406301402.42119.jhb@freebsd.org> <8BA1A243-8EA9-449A-A2D2-4E03487CE3E0@sarenet.es>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Regards
Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5481AC78.6050107>