I just hate it when I test a new version of NetBSD on a couple of machines successfully, and only run into trouble when I push the ugprade to a busy server. After upgrading the server where these pages live to 3.99.1 the machine paniced in the TCP/SACK routines roughly once every 36 hours (really has to do with the traffic, not time). I tried upgrading again, to 3.99.3, but that was worse: the machine would hang within 2 hours. Now I’ve downgraded back to 3.99.1 and disabled SACK, hoping to get a stable environment.
I’m still running 2.99.15 on other busy machines, and it has been very solid — I cannot recall a single panic, hang or crash. It’s just that a) somebody needs to test the new stuff, b) I keep hearing things like “it only happens on your machine” (ugh) and c) holding off from upgrading for too long tends to make for painful upgrades. However, it might still be possible to convince me to run the netbsd-3 stable branch…
So if you can’t read this, please check back soon — I’m just recovering from a panic. :-)
Hmm.. very strange. We’re experiencing the same trouble, random hangs within a few hours. It hardly could be a traffic issue, this is a low loaded intranet ftp archive. No activity on netbsd mailing lists too…
Eugene — 4.5.05 @ 17:33
Well, I’m still happy with 3.99.1 with SACK disabled (although having SACK would be nice). I’m deferring updates until after I’m settled at my new home, some time in the fall.
From what I’ve heard, it might be beneficial to upgrade to the latest, but personally I think that could always go either way… :-)
Kimmo Suominen — 28.5.05 @ 16:09