On Tue, Sep 28, 2010 at 11:08:24PM +0100, a.sm...@ukgrid.net wrote: > Quoting Pyun YongHyeon <pyu...@gmail.com>: > > > However don't apply the patch to production box. > > > > Hi, > > actually the only server of this type is a production box, it was > originally running FreeBSD 7.2 without issue but was upgraded when 7.2 > went EOL. > What would you recommend? I guess I can wait for this to be tested by
I don't think it would cause severe problem with the patch but it was not heavily tested under various network load so this is the main reason why I took precaution against applying it on production box. If you're prepared to go back to old working kernel and it's tolerable for small down time you may go that route. > someone else as it doesnt seem to be causing and severe issues. The As I said, the patch requires another patch that handles shared interrupt with tagged status. I also have initial patch for that but it needs more polishing and cleanups. Lack of controller that has this issue also makes it hard to write patch. Your controller has no such issue so I wanted to know whether you're seeing known hardware errata or not. > server in question is running wordpress-mu and I havent had any > complaints from end users about this, > > thanks Andy. > > > > _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
