From owner-freebsd-stable Fri May 7 18:21:14 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 5471F14CE0 for ; Fri, 7 May 1999 18:21:12 -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 SAA00653 for ; Fri, 7 May 1999 18:21:14 -0700 (PDT) Date: Fri, 7 May 1999 18:21:14 -0700 (PDT) From: Cliff Skolnick X-Sender: cliff@lazlo.internal.steam.com To: freebsd-stable@FreeBSD.ORG Subject: lockup problem maybe fixed by patch in kern/8416 In-Reply-To: <199905072200.PAA20019@implode.root.com> 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 So I grabed the latest kernel this AM, and installed it without the patch in PR kern/8416. Poof! lockup within 8 hours! I had been running since monday (3+ days) without a deadlock when that patch was installed as opposed to locking up 4 times over 3 days. Needless to say I put the patch back in now, and I'm hoping that was it...granted this sample set is small. If other people are having a lockup problem, you might want to use the later patch in PR kern/8416. It's the patch to kern_lock.c, it would be interesting if that helped other people. Cliff On Fri, 7 May 1999, David Greenman wrote: > >My deadlock problems started with a cvsup a little over a week ago, and many > >others also noted that the problem started in april. Before that, my 3.1 > >system was rock solid. It's either a VM problem or a CAM problem by how the > >system responds to pings for a bit, but no disk acces can be done. No > >console messages, the machine is a server and not running X. > > > >Perhaps something bad got checked in in April, this weekend I'm going to > >spend some time looking a what actually changed that month. > > > >I'm also a little alarmed about how many people are rationalizing this and > >attacking the posters of lockup problems. Many posters have stated that > >there sysem was stable with 2.2 or an earlier version of 3.1, please don't > >discount that. This is -stable, not -advocacy. > > > >QUESTION FOR THE GURUS > > > >I'd love to get a system snapshot or something while the kernel is still > >running. Is there a way to do this once the disk system is out to lunch? > >Hints? > > Put DDB into your kernel. When the system hangs, enter the debugger with > ctrl-printsceen. You can then use the 'ps', 'trace', and 'panic' commands. > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org > Creator of high-performance Internet servers - http://www.terasolutions.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- Cliff Skolnick Steam Tunnel Operations cliff@steam.com http://www.steam.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message