From owner-freebsd-acpi@FreeBSD.ORG Thu Jun 21 08:48:06 2007 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0EDA516A468 for ; Thu, 21 Jun 2007 08:48:06 +0000 (UTC) (envelope-from olivier@aixmarseille.com) Received: from anchor.aixmarseille.com (anchor.aixmarseille.com [81.201.184.34]) by mx1.freebsd.org (Postfix) with ESMTP id CD36C13C484 for ; Thu, 21 Jun 2007 08:48:05 +0000 (UTC) (envelope-from olivier@aixmarseille.com) Received: from pleiades4.data-mobiles.com ([194.250.124.77] helo=[10.0.0.219]) by anchor.aixmarseille.com with esmtpsa (TLS-1.0:RSA_ARCFOUR_MD5:16) (Exim 4.50) id 1I1IKg-0001PI-N2 for freebsd-acpi@freebsd.org; Thu, 21 Jun 2007 08:48:02 +0000 From: Olivier Fauchon To: freebsd-acpi@freebsd.org In-Reply-To: <1182328473.1054.14.camel@localhost> References: <1182251419.985.22.camel@localhost> <4677F41A.7040803@root.org> <1182328473.1054.14.camel@localhost> Content-Type: text/plain Date: Thu, 21 Jun 2007 10:47:58 +0200 Message-Id: <1182415678.1108.9.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: Help required for HP NC6000 Suspend on Ram Troubleshooting X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2007 08:48:06 -0000 .... > ath0: link state changed to DOWN > wakeup from sleeping state (slept 00:00:03) > .... > > So I guess my system pass the test. > Yep. > > > 2/ When doing a 'regular' acpiconf -s3 , system goes black, > I can hear 3 'beeps', and then the laptop is stuck (Requires > hard reboot). > > In fact the led should be red blinking in suspend mode, > but it's still permanant green. > > My guess is that the system can't call properly S3 ACPI Suspend code??? > > > Any more help required :-) > Weird.. the key is to figure out what's happening during the final entry to S3. You could try throwing in some printfs and see what was the last to trigger. -- Nate