From owner-freebsd-current Wed Sep 13 13:26:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA25431 for current-outgoing; Wed, 13 Sep 1995 13:26:58 -0700 Received: from covina.lightside.com (covina.lightside.com [198.81.209.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id NAA25424 for ; Wed, 13 Sep 1995 13:26:54 -0700 Received: by covina.lightside.com (Smail3.1.28.1 #6) id m0ssyOR-0009XtC; Wed, 13 Sep 95 13:26 PDT Date: Wed, 13 Sep 1995 13:26:51 -0700 (PDT) From: Jake Hamby To: current@freebsd.org Subject: Yet another severe Sig 11 problem with -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk I just upgraded to -current (as of 10:00 pm Sept. 12 PDT) and compiled it on my Micron 90MHz Pentium at work to see if my machine could shed any light on the Sig-11 problem so many people have reported. I built a custom kernel and rebooted, and sure enough, sig 11's on the two sed's in rc.local and sig 11's on login which locked my out of the system! This is a severe problem, and not at all like the occasional sig 11's that some people have reported. Here is some information on my system if this might help solve the problem: Micron 90MHz Pentium PCI/ISA w/ 32MB RAM BusLogic PCI SCSI controller with Conner 1GB hard drive & Plextor CDROM 3COM 3c509 ISA Ethernet card new-style 2.0.5-RELEASE startup scripts. The only LKM was the screensaver module which was rebuilt by make world, and the Sig 11's still occured when I removed it. It makes no difference whether I use a custom config or GENERIC. Anyway, good luck in finding the problem. I'm going to revert back to my 2.0.5-RELEASE kernel until you solve it. If you need any more information about my configuration, let me know. ---Jake Hamby jehamby@lightside.com