So there was some discussion recently about SMP boxes spontaneously rebooting with no crash dump logged. as someone considering upgrading to 4.9 i naturally have some reservation and concern. Can folks comment on 4.9 stability and SMP. Are these rare fluke cases or a more common occurrence? Thanks, -j
4.9-STABLE has been nothing but rock solid (except where hardware was flaky) on all, mostly Dell, SMP boxes i've run it on. freebsd only got crashy on SMP boxes with funky RAID controllers using 5.2.1, which didn't claim to be stable. :) jon Jeff Johnson wrote:> So there was some discussion recently about SMP boxes spontaneously > rebooting with no crash dump logged. > > as someone considering upgrading to 4.9 i naturally have some > reservation and concern. > > Can folks comment on 4.9 stability and SMP. > Are these rare fluke cases or a more common occurrence? > > Thanks, > > -j > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >
Jeff Johnson wrote:> Can folks comment on 4.9 stability and SMP. > Are these rare fluke cases or a more common occurrence?I'm running 4-stable on several boxes. [217]~ >rsh ungoverned "uptime" 11:31AM up 173 days, 39 secs, 0 users, load averages: 0.20, 0.13, 0.09 [218]~ >uptime 11:31AM up 44 days, 22:53, 3 users, load averages: 0.22, 0.17, 0.17 [219]~ >rsh tinker "uptime" 11:31AM up 76 days, 1:40, 2 users, load averages: 0.02, 0.01, 0.00 All are running 4.9 and all are dual-processor boxes of different flavors. I think "rare fluke cases" is probably closer to reality. _I_ certainly haven't seen such a problem. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/
Jeff Johnson wrote:> So there was some discussion recently about SMP boxes spontaneously > rebooting with no crash dump logged.Yes this is a fact.> as someone considering upgrading to 4.9 i naturally have some > reservation and concern.Do you need anything that 4.9 offers?> Can folks comment on 4.9 stability and SMP. > Are these rare fluke cases or a more common occurrence?I was up for over 130 days on 4.8-STABLE The longest FreeBSD 4.9-STABLE could stay up was *no more than 48 hours*. Since I downgraded to FreeBSD 4.8-RELEASE-p17 #0 Uptime 4 days, 12 hours, 53 minutes So far so good.... check back in another 100 days Rick
> Can folks comment on 4.9 stability and SMP. > Are these rare fluke cases or a more common occurrence?I'm running 4.9-STABLE on a Supermicro P6DGH, up 14+ days since the last reboot (had to replace a bad SCSI disk in a vinum array). Mike Squires
Jeff Johnson wrote:> So there was some discussion recently about SMP boxes spontaneously > rebooting with no crash dump logged. > > as someone considering upgrading to 4.9 i naturally have some > reservation and concern. > > Can folks comment on 4.9 stability and SMP. > Are these rare fluke cases or a more common occurrence? > > Thanks, > > -j >This has been an ongoing discussion since 4.9 was released. Our hope is that 4.10 will address these stability problems. If you are interested, please try out 4.10-BETA and see how it works for you. Scott
Rick Updegrove wrote:> Jeff Johnson wrote: > >> So there was some discussion recently about SMP boxes spontaneously >> rebooting with no crash dump logged. > > > Yes this is a fact. > >> as someone considering upgrading to 4.9 i naturally have some >> reservation and concern. > > > Do you need anything that 4.9 offers? > >> Can folks comment on 4.9 stability and SMP. >> Are these rare fluke cases or a more common occurrence? > > > I was up for over 130 days on 4.8-STABLE > > The longest FreeBSD 4.9-STABLE could stay up was *no more than 48 hours*. >What was the date of your 4.9-STABLE system? Would you be willing to give 4.10-BETA a try? It would really help us know if we are ready to release 4.10 or not. Scott
Scott Long wrote: > What was the date of your 4.9-STABLE system? Would you be willing> to give 4.10-BETA a try? It would really help us know if we are ready > to release 4.10 or not.I hesitate to do this since my problem is *fixed* with root@govmail ~ # uname -v FreeBSD 4.8-RELEASE-p17 #0: Sun Apr 4 23:57:39 PDT 2004 root@govmail ~ # uptime 10:12AM up 8 days, 9:19, 1 user, load averages: 0.41, 0.56, 0.49 I absolutely love FreeBSD 4.x and depend upon it for my all my server needs, and FreeBSD 4.x is all I have used for many years now. This year I finally started using it exclusively for my desktops at home, (soon to be on my desktop at work also but here I took the plunge and installed two 5.x boxes). I strongly feel it is my duty and responsibility to help out wherever I can, so I will cvsup right now to: *default release=cvs tag=RELENG_4_9 This will give me the 4_10 BETA ? Rick
On Tue, Apr 13, 2004 at 10:19:03AM -0700, Rick Updegrove wrote:> I strongly feel it is my duty and responsibility to help out wherever I > can, so I will cvsup right now to: > > *default release=cvs tag=RELENG_4_9 > > This will give me the 4_10 BETA ?No -- you need *default release=cvs tag=RELENG_4 for that. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20040413/4158f637/attachment.bin
Scott Long wrote:> What was the date of your 4.9-STABLE system? Would you be willing > to give 4.10-BETA a try? It would really help us know if we are ready > to release 4.10 or not.I followed my "usual" method and "make -j4 buildworld" got stuck here. gcc -O -pipe -D_GNU_SOURCE -I. -I/usr/src/gnu/usr.bin/binutils/libbinutils -I/usr/src/gnu/usr.bin/binutils/libbinutils/../libbfd/i386 -I/us r/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/include -DTARGET=\"i386-unknown-freebsd\" -DBFD_VERSION_STRING=\""2.12.1 [FreeBSD] 2002-07-20"\" -I/usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/binutils -I/usr/src/gnu/usr.bin/binutils/l ibbinutils/../../../../contrib/binutils/bfd -D__FBSDID=__RCSID -c arlex.c -o arlex.o cpp0: output pipe has been closed gcc: Internal compiler error: program cc1 got fatal signal 11 *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 Before anyone tells me that "fatal signal 11" is my hardware keep in mind I built FreeBSD 4.8-RELEASE-p17 #0: Sun Apr 4 23:57:39 PDT 2004 (and all the other 4.8 series) without running into this problem. Although, to be accurate I think I always booted to the "original single CPU kernel" to do this. Ok I am booting to /kernel.GENERIC and before I "cd /usr/src; make -j4 buildworld" should I start all over from scratch? Please advise. Rick
Rick Updegrove wrote:> Scott Long wrote: > >> What was the date of your 4.9-STABLE system? Would you be willing >> to give 4.10-BETA a try? It would really help us know if we are ready >> to release 4.10 or not. > > > I followed my "usual" method and "make -j4 buildworld" got stuck here. > > gcc -O -pipe -D_GNU_SOURCE -I. > -I/usr/src/gnu/usr.bin/binutils/libbinutils > -I/usr/src/gnu/usr.bin/binutils/libbinutils/../libbfd/i386 -I/us > r/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/include > -DTARGET=\"i386-unknown-freebsd\" -DBFD_VERSION_STRING=\""2.12.1 > [FreeBSD] 2002-07-20"\" > -I/usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/binutils > > -I/usr/src/gnu/usr.bin/binutils/l > ibbinutils/../../../../contrib/binutils/bfd -D__FBSDID=__RCSID -c > arlex.c -o arlex.o > cpp0: output pipe has been closed > gcc: Internal compiler error: program cc1 got fatal signal 11 > *** Error code 1 > 1 errorHave a look at your /var/log/messages file. You may have run out of swap space. If so, you can create a file as (temporary) extra swap space, to let the compilation successfully end; see the handbook for details. R.
Rob wrote:> Have a look at your /var/log/messages file. You may have run out of swap > space.Thanks Rob. I always read all the logs : ) The only thing in messages was: Apr 13 14:09:52 govmail /kernel: pid 43747 (cc1), uid 0: exited on signal 11 (core dumped)> If so, you can create a file as (temporary) extra swap space, to let the > compilation successfully end; see the handbook for details.Looks ok to me: Disk Swap 0% 1008.41 MB 144.00 KB 1008.55 MB I did reboot to the single CPU 4.8-RELEASE kernel and it built fine. Then I accidentally hit up arrow and it started make -j4 buildword again so I am letting it finish (again) I will post the results of the new kernal etc soon. Rick
On Wed, Apr 14, 2004 at 03:37:45PM -0700, Rick Updegrove wrote:> Rick Updegrove wrote: > > > I am now runing: > > FreeBSD 4.10-BETA #0: Tue Apr 13 21:49:08 PDT 2004 > > > > I hope it works better than 4.9 : ) > > Ok it crashed and rebooted already... > > I am done with the beta testing of 4.10Thanks for not providing useful details :( Kris -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20040414/689dc7a4/attachment.bin
Kris Kennaway wrote: > Thanks for not providing useful details :( Sorry Kris, I was never able locate any useful info about why this is happening on my own, which is why I reverted back to 4.8 in the first place. What would you like, *exactly*? I have the rest of the night but this machine has to go back into production *soon*. I am willing to provide whatever you specifically ask for but I need some help. In fact someone is going to need to hold my hand through some of these steps, so if anyone is willing I have all night. Rick
# dislists@updegrove.net / 2004-04-14 16:37:13 -0700:> Kris Kennaway wrote: > > Thanks for not providing useful details :( > > Sorry Kris, > > I was never able locate any useful info about why this is happening on > my own, which is why I reverted back to 4.8 in the first place. > > What would you like, *exactly*? I have the rest of the night but this > machine has to go back into production *soon*. I am willing to provide > whatever you specifically ask for but I need some help. In fact someone > is going to need to hold my hand through some of these steps, so if > anyone is willing I have all night.http://www.freebsd.org/doc/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING http://www.freebsd.org/doc/books/developers-handbook/kerneldebug.html (heading straight to bed) -- FreeBSD 4.9-RELEASE-p2 1:08AM up 18:35, 3 users, load averages: 0.01, 0.02, 0.00