From owner-freebsd-stable Thu May 7 16:32:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01405 for freebsd-stable-outgoing; Thu, 7 May 1998 16:32:42 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from natsoft.com.au (natsoft.com.au [203.39.138.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01164; Thu, 7 May 1998 16:31:41 -0700 (PDT) (envelope-from craig@natsoft.com.au) Received: from Win95.natsoft.com.au (Win95 [203.39.138.131]) by natsoft.com.au (8.8.5/8.8.5) with SMTP id KAA05483; Fri, 8 May 1998 10:34:01 GMT Message-ID: <35524411.523E@natsoft.com.au> Date: Fri, 08 May 1998 09:30:25 +1000 From: Craig Wilson Organization: National Software Pty Ltd X-Mailer: Mozilla 3.04 (Win95; I) MIME-Version: 1.0 To: Studded CC: freebsd-stable@FreeBSD.ORG, phk@FreeBSD.ORG, dg@root.com Subject: Re: FreeBSD 2.2.6-RELEASE References: <35502381.7A27@natsoft.com.au> <3552243B.15AAF366@san.rr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Studded wrote: > > > > > kern/4844 VM lookup, endless loop in vm_map_lookup_lookup_entry() > > this PR was closed on Apr26 1998 > > Poul was the one who closed this with "fixed in -current." He's the one > who should be able to tell you if it's fixed in -stable. Given that > 2.2.6-Release was cut in march, this PR is certainly not fixed in that > release. > > > kern/6258 VM lookup on kernel map........ > > this PR was closed on Apr26 1998 > > Similar situation with this one, fixed after 2.2.6-Release. It's also > closed by poul with "fixed in -current" in spite of the fact that the > audit trail has David Greenman asking for the fix to be applied to > -Stable. > Thankyou for your assistance. Maybe I had better stay with 2.2.2-RELEASE than use 2.2.6 without the above patches. 2.2.2 is working 100% stable for me, so why change? I will look at 2.2.7-RELEASE when it is available. Just something else I would like to note. I installed 2.2.6-RELEASE from CDROM onto a 486/66 Compaq EISA machine with an IDE hard drive and with 8 meg ram. While I was building a custom Kernel on ttyv1 I was using vi on ttyv2. When I exited vi the system froze for approx 20 seconds, except that I could still change from ttyv2 to ttyv1 with ALT F2 etc. ttyv0 had a login message, however I could not login to it, ie no keyboard echo. After the 20 secs the system returned to normal. Has anyone seen this before? Thanks in advance for any information. Regards Craig Wilson National Software Pty Ltd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message