On 17 Jan 2013, at 20:27, Devin Teske <devin.te...@fisglobal.com> wrote:
> > On Jan 17, 2013, at 11:14 AM, Steven Hartland wrote: > >> ----- Original Message ----- From: "Devin Teske" <devin.te...@fisglobal.com> >>> You're the perfect person to help us figure out why when we: >>> >>> 1. back-port mfi(4) from stable/8 into releng/8.3 (8.3-RELEASE-p5 at the >>> time of back-port) >>> >>> 2. Succeed in getting 8.3 to boot on Thunderbolt card >>> >>> 3. mfiutil produces Inappropriate ioctl for device >>> >>> Even after… >>> >>> 4. Recompiling mfiutil from stable/8 (albeit in a releng/8.3 build >>> environment -- back ported headers applied for new macros even) >>> >>> Any hints on where to go next to restore mfiutil access? >> >> You also need to backport mfiutil too. >> >> I have a patch set for 8.3 which include latest mfi driver, mfiutil and >> a large set of mfi driver fixes, even head has some rather serious issues >> although mainly around error handling on tbolt cards. >> >> We're running this in production so believe its a good stable set. >> >> If you would like the patch set just let me know. >> > > I can't resist when you combine words like "production" and "8.3" (smiles) > ? Are you saying 8.3 isn't production worthy ? Works like a charm here for us. 50+ boxes running 8.x, most of which are 8-stable. No offence meant, but I'd take 8.3 over 9.x any day. Any night too, for that matter. YMMV but PF + pfsync + carp (and some boxes with nginx or relayd on top) is pretty good for our workload on 8.3. _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
