From owner-freebsd-stable Mon May 10 13:18:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from lazlo.internal.steam.com (lazlo.steam.com [199.108.84.37]) by hub.freebsd.org (Postfix) with ESMTP id 305F514BF5 for ; Mon, 10 May 1999 13:18:15 -0700 (PDT) (envelope-from cliff@steam.com) Received: from lazlo.internal.steam.com (cliff@lazlo.internal.steam.com [192.168.32.2]) by lazlo.internal.steam.com (8.9.3/8.9.3) with ESMTP id NAA05915; Mon, 10 May 1999 13:17:39 -0700 (PDT) Date: Mon, 10 May 1999 13:17:35 -0700 (PDT) From: Cliff Skolnick X-Sender: cliff@lazlo.internal.steam.com To: Mike Tancsa Cc: Cy Schubert - ITSD Open Systems Group , freebsd-stable@FreeBSD.ORG Subject: Re: vm_fault deadlock and PR 8416 (was Re: Strange reboot saga ) In-Reply-To: <3.0.5.32.19990510151933.017f1b90@staff.sentex.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems to have solved my deadlock problems. I'm running w/o it now, ready to try to go into the debugger after the next lockup. I'm expecting it within a few hours. Cliff On Mon, 10 May 1999, Mike Tancsa wrote: > At 12:11 PM 5/10/99 -0700, Cy Schubert wrote: > >I remember trying this exploit about a month ago when it was first > >announced. It locked the system up solid within seconds. After > >applying the patches from PR 8416 I currently have four copies of > >find and one tripwire running for over an hour and a half, with no > >hang. The patches from PR 8416 appear to have fixed the hang. > > > That is most excellent... Is there any reason why this patch has not been > applied to the tree ? i.e. does it have any adverse side effects > preventing it from being committed ? > > ---Mike > > > >In message <4.1.19990509174640.0534ef10@granite.sentex.ca>, Mike > >Tancsa writes: > >> At 05:05 PM 5/9/99 , Cy Schubert - ITSD Open Systems Group wrote: > >> > > >> >In message <19990507220718.B31932@relay.ucb.crimea.ua>, Ruslan Ermilov > >> >writes: > >> >> Just FYI: > >> >> > >> >> $ uname -r; uptime > >> >> 2.2.1-RELEASE > >> >> 10:02PM up 115 days, 5:57, 1 user, load averages: 0.00, 0.09, 0.14 > >> >> (last reboot was due to ) > >> >> > >> >> $ uname -r; uptime > >> >> 3.1-STABLE > >> >> 10:02PM up 8 days, 11:07, 6 users, load averages: 0.27, 0.17, 0.11 > >> >> (last reboot was due to system freeze) > >> > > >> >You know the strange thing about these freezes is that they don't occur > >> >on every system. For example, I manage four 3.1R systems and a 2.2.8R > >> >system. Three of the 3.1 systems are rock solid. The fourth one, > >> >which also happens to have the fastest clock speed (333MHz PII in a > >> >Dell), has frozen four times since February while I was running > >> >tripwire 1.3 with -interactive, during phase 4 file checks, and > >> >starting netscape, and restoring exmh2 from an icon. The system is > >> >doing A LOT of paging at the time of the hangs. PR 8416 might hold > >> >some promise of fixing this. > >> > >> Perhaps its related to the mmap bug.. I think I have been hit by it once on > >> one of my systems... > >> > >> e.g. > >> find / -type f -exec grep zztop "{}" \; & > >> find / -type f -exec grep zztop "{}" \; & > >> > >> will lock a 3.x box solid. > > ------------------------------------------------------------------------ > Mike Tancsa, tel 01.519.651.3400 > Network Administrator, mike@sentex.net > Sentex Communications www.sentex.net > Cambridge, Ontario Canada > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- Cliff Skolnick | "They that can give up essential liberty to obtain Steam Tunnel Operations | a little temporary safety deserve neither liberty cliff@steam.com | nor safety." http://www.steam.com/ | -- Benjamin Franklin, 1759 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message