From owner-freebsd-bugs@FreeBSD.ORG Wed Mar 17 11:40:08 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBE4816A4D0 for ; Wed, 17 Mar 2004 11:40:08 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D271743D2F for ; Wed, 17 Mar 2004 11:40:08 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i2HJe8bv040001 for ; Wed, 17 Mar 2004 11:40:08 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i2HJe817040000; Wed, 17 Mar 2004 11:40:08 -0800 (PST) (envelope-from gnats) Date: Wed, 17 Mar 2004 11:40:08 -0800 (PST) Message-Id: <200403171940.i2HJe817040000@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Jesse Guardiani Subject: Re: misc/59876: APM suspend/resume broken with FreeBSD 5.2-BETA on IBM Thinkpad A30p X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jesse Guardiani List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Mar 2004 19:40:09 -0000 The following reply was made to PR misc/59876; it has been noted by GNATS. From: Jesse Guardiani To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: misc/59876: APM suspend/resume broken with FreeBSD 5.2-BETA on IBM Thinkpad A30p Date: Wed, 17 Mar 2004 14:38:47 -0500 I've been running 5.2.1-RELEASE for about a week now. I ran 5.2.1-RC2 for a few weeks before this. Both versions: a.) Do NOT exhibit the "Crash every time on resume unless booted with `boot -vD`" behavior that I experienced under 5.2-RELEASE. b.) DO crash every fourth or fifth resume. This is a regression from 5.1-RELEASE under which my machine used to crash every 8 or 10 resumes. It's also technically a regression from the reliability I got with `boot -vD` under 5.2-RELEASE, but at least 5.2.1-RELEASE boots without that kind of hackery. I suppose this ticket can be closed now. I'm still having problems, but they're much different in nature from the original reason this ticket was created. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net