Date: Wed, 22 Feb 1995 12:53:50 -0600 (CST) From: John Lind <john@starfire.mn.org> To: questions@FreeBSD.org Subject: sh and csh SIGSEGV on exit in 2.0-950210-SNAP Message-ID: <199502221853.MAA18611@starfire.mn.org>
next in thread | raw e-mail | index | archive | help
This is primairly FYI for the development team -- it isn't happening often enough to be a real problem for us at this time, and we understand that the SNAPs are development code. Every once in awhile, either csh or sh will SIGSEGV as they are perparing to exit (after EOF or an exit command), either interactively or when run from make. Attempting to recreate the same circumstances will not (usually) result in the same behavior. This is a very, very teeny 486DX2/66 system, with 16Mb of swap and 4Mb of RAM. It also reports early in the boot process that the installed reported real memory of 640K does not match the RTC value of 639K. This is a Packard Bell Legend 1166 and I still haven't found how to manipulate things that one might want to manipulate like the bus timing equations and any shadowing that may be going on -- it doesn't have cold boot ROM support for configuration, but it has a hot key sequence of Alt-Ctrl-S for basic CMOS stuff (though not the advanced features). This system SOMETIMES comes up reporting stray intr 7 up until the warning limit is reached (quite quickly). Obviously, this system was not purchased with FreeBSD in mind, but it belongs to the family of a CS major who is very excited about running something other than Windoze on this box. John Lind, Starfire Consulting Services E-mail: john@starfire.MN.ORG USnail: PO Box 17247, Mpls MN 55417
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199502221853.MAA18611>