I just upgraded a test server to STABLE from today (good friday, around mid-day GMT), and though it all came up without errors I could not get any network connectivity out of the machine. The ethernet uses lagg to bindle two bce interfaces together - I know here were updates to the bce drive recently, but I have not been able to try them in isolation. The box in question is an HP ProLiant DL360 G5, and I spent some time trying to get some life out of it, but to no avail. I have had to roll this back for now so can't investigate further unfortunately. Sorry, I know this is a fairly useless bug report, but I wanted to at least get the info out there that this doesn't work. Will try again when I have a bit more access to the maachine. Anyone else seen similar ? -pete.
I found a machine wityh identical hardware that wasn't using lagg, and have tested there to see if bce on it's own works. It does. So noew I am wondering if... a) Does something in the new bce changes stop it working ith lagg? b) Is there something broken in lagg indepeendent of bce? c) Is my config slightly wrong, but that didnt show up until now? Can someone remind me when the bce chnages went into STABLE so I can try a 'before' /'after' test to see if a) is true ? cheers, -pete.
Ok, I have now confirmed that the commit mentioned in this email: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=187270+0+archive/2009/freebsd-stable/20090405.freebsd-stable ss what breaks lagg using bce on my machines. I did submit a PR about this, but I can't find it yes (though I dont know how long such things take to show up, this was only ten minutes ago or so). Code before the commit works, code after doesn,t and it is only the bce files which have changed. I wrote "stable" in the subject line, but this is present in the 7.2 prerelease stuff, and is a regression from 7.1 (a fairly major one in my opinion, but I realise ever problem is importnat to the person it affects). cheers, -pete.