Date: Sat, 7 Jun 2008 13:09:06 -0700 From: Jo Rhett <jrhett@netconsonance.com> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 Message-ID: <26AD2497-B8BA-47CD-8802-FA354738A674@netconsonance.com> In-Reply-To: <200806051023.56065.jhb@freebsd.org> References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <200806051023.56065.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, John. Thanks for your update and I'll keep your experience in mind. As stated in previous messages, I'll open new threads in the appropriate lists about any specific driver issues (with details) that I am concerned about. This thread was intended to deal with the overall policy issue for dropping 6.2 in just barely more than a year.. On Jun 5, 2008, at 7:23 AM, John Baldwin wrote: > On Wednesday 04 June 2008 01:20:56 pm Jo Rhett wrote: >> Okay, I totally understand that FreeBSD wants people to upgrade from >> 6.2 to 6.3. But given that 6.3 is still experiencing bugs with >> things >> that are working fine and stable in 6.2, this is a pretty hard case >> to >> make. >> >> This is also a fairly significant investment in terms of time and >> money for any business to handle this ugprade. It totally understand >> obsoleting 5.x now that 7.x is out. But 6.2 is barely a year old... > > FWIW, at Y! 6.3 is more stable than 6.2 (I had a list of about 10 > patches for > known deadlocks and kernel panics that were errata candidates for > 6.2 that > never made it into RELENG_6_2 but all of them are in 6.3). We also > have many > machines with bge(4) and from our perspective 6.3 has less issues > with bge0 > devices than 6.2. > > Given the real world experience I have, your claims of instability w/ > o even > testing 6.3 border on silly. Also, when it comes to bge(4), you > need to be > _very_ specific about what chipsets you are using and comparing > those with > the chipsets in the bug reports you read. The bge(4) driver in > particular > covers a vast range of different hardware variations and is a bit of a > hodge-podge itself. If there is a problem with a 5705 card then it > may be > specific to just 5705 parts and not affect 575x, etc. parts. > > Again, with 3ware, there are two different drivers (twe(4) vs > twa(4)) and > again, you need to be more specific with which driver you are using > and which > model controllers you have. > > -- > John Baldwin -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26AD2497-B8BA-47CD-8802-FA354738A674>