Date: Wed, 04 Oct 2006 02:19:32 -0600 From: Scott Long <scottl@samsco.org> To: Dermot Williams <dermot@irishbroadband.ie> Cc: Fredrik Widlund <fredrik.widlund@qbrick.com>, freebsd-current@freebsd.org Subject: Re: 6.2-BETA2 Dell PE1950 Message-ID: <45236E94.5080308@samsco.org> In-Reply-To: <1159948998.5170.6.camel@localhost.localdomain> References: <4522E54C.7060406@qbrick.com> <1159948998.5170.6.camel@localhost.localdomain>
next in thread | previous in thread | raw e-mail | index | archive | help
A quick tour of the bce driver leaves a lot of concerns in my mind about how interrupts are handled as well as how work is segmented. I only have very limited access to a 1950 with this chip in it, though, so if anyone can provide better access (or maybe a shiny new 1950 for my lab!) I can look at it over the next week or so. Scott Dermot Williams wrote: > Frederik, > > Dunno if it helps, but we're running 6.1-STABLE on 1950s and the mfi > driver detects the SAS with no problems. > > With regard to the bce driver, I've been having the exact same issue on > this hardware - NFS triggers it every time in our case. I've upgraded > one of the machines in question to one of the 7- releases and the > problem is still there, unfortunately. > > I've actually ordered Intel PRO cards for these 1950s because we're in > the same boat as you in that we don't really want to migrate away from > FreeBSD. > > Sorry I don't have more or better info for you. > > Regards, > > Dermot > > On Wed, 2006-10-04 at 00:33 +0200, Fredrik Widlund wrote: >> Hi, >> >> I'm trying to get FreeBSD working on Dell 1950 (and 2950), which is >> vital since it's no longer possible to buy 1850/2850 units here. >> >> Hardware: >> PE1950 Xeon 5130, 2GB 667MHz >> SAS 5I >> PERC5E >> >> 6.1-RELEASE: not possible since SAS drives aren't found. >> 6.2-BETA2: bce interfaces does not work at all, "watchdog timeout >> occured" every other second, and _no_ connectivity. >> >> We are also having problems with some PE1850 failing from time to time >> with "watchdog timeout" hangs, and have had to debug.mpsafenet=0 these. >> >> How can we help solve this issue? It would really be a pity to be forced >> to leave FreeBSD but we really can't afford to replace our choice of >> hardware platform. >> >> Kind regards, >> Fredrik Widlund >>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45236E94.5080308>