From owner-freebsd-mobile Thu Aug 16 11:45:38 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mtiwmhc25.worldnet.att.net (mtiwmhc25.worldnet.att.net [204.127.131.50]) by hub.freebsd.org (Postfix) with ESMTP id BCBF637B408 for ; Thu, 16 Aug 2001 11:45:33 -0700 (PDT) (envelope-from parv@worldnet.att.net) Received: from worldnet.att.net ([32.100.199.21]) by mtiwmhc25.worldnet.att.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010816184531.FAJB5127.mtiwmhc25.worldnet.att.net@worldnet.att.net>; Thu, 16 Aug 2001 18:45:31 +0000 Received: by worldnet.att.net (Postfix, from userid 1001) id ABD1650F46; Thu, 16 Aug 2001 14:45:32 -0400 (EDT) Date: Thu, 16 Aug 2001 14:45:32 -0400 From: parv To: David Wolfskill Cc: mobile@freebsd.org Subject: Re: dell i5000e & apm Message-ID: <20010816144532.A2752@moo.holy.cow> Mail-Followup-To: David Wolfskill , mobile@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200108151731.f7FHVSw82368@bunrab.catwhisker.org>; from david@catwhisker.org on Wed, Aug 15, 2001 at 10:31:28AM -0700 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org this was, on the fateful occasion around Aug 15 13:31 -0400, sent by David Wolfskill > > >Date: Wed, 15 Aug 2001 10:04:12 -0400 > >From: parv > > >is there a soul here who knows if freebsd 4-stable on dell inspiron > >5000e can survive more than one "stand by/suspend" cycles, measured in > >minutes, w/o hard reboots? > > >last time i tried, when dell issued an bios-apm update, around may 6 > >2001 w/ then current 4-stable version, the exercise was in futility. > > OK; I finally got a chance to try this on my laptop (which is quite > similar to a Dell I5000e), and it seems to work just fine: I used > Fn+Esc to suspend (to RAM; I don't have suspend-to-disk set up), waited > a while, then tapped the power button to wake it up. I didn't even need > to do anything with Fn+F8. > > This is on: > FreeBSD m147.whistle.com 4.4-PRERELEASE FreeBSD 4.4-PRERELEASE #147: Wed Aug 15 06:38:39 PDT 2001 i have installed 4.4-prerelease, and i have good news & bad news. good news is that standby/suspend worked w/o problems for 1-2 hours. i issued apm -Z, which after some entered into suspend mode. recovery was ok. before that 4-5 short cycles, 10-50 seconds, of standby/suspend modes didn't cause any problems. later, when i woke up the computer after 11-12 hours in suspend mode, everything was ok, but about 5 or so minutes later system decided to reboot. but could be user error as at the time i was playing w/ Fn+Suspend keys? here is the apmd log... Aug 15 23:56:51 moo apmd[227]: start Aug 15 23:58:46 moo apmd[227]: apmevent 000b index 1 Aug 15 23:58:48 moo apmd: resumed at 20010815 23:58:48 Aug 15 23:59:21 moo apmd[227]: apmevent 000b index 2 Aug 15 23:59:21 moo apmd: resumed at 20010815 23:59:21 Aug 16 00:00:21 moo apmd[227]: apmevent 0003 index 3 Aug 16 00:00:21 moo apmd: resumed at 20010816 00:00:21 Aug 16 00:01:50 moo apmd[227]: apmevent 0003 index 4 Aug 16 00:01:50 moo apmd: resumed at 20010816 00:01:50 Aug 16 00:02:24 moo apmd[227]: apmevent 000b index 5 Aug 16 00:02:24 moo apmd: resumed at 20010816 00:02:24 Aug 16 00:03:21 moo apmd[227]: apmevent 000b index 6 Aug 16 00:03:21 moo apmd: resumed at 20010816 00:03:21 Aug 16 00:04:48 moo apmd[227]: apmevent 0003 index 7 Aug 16 00:04:48 moo apmd: resumed at 20010816 00:04:48 Aug 16 00:36:47 moo apmd[227]: apmevent 000b index 8 Aug 16 00:36:47 moo apmd[227]: apmevent 0002 index 9 Aug 16 00:36:47 moo apmd: resumed at 20010816 00:36:47 Aug 16 00:36:48 moo apmd: suspend at 20010816 00:36:48 Aug 16 01:35:06 moo apmd[227]: apmevent 0003 index 10 Aug 16 01:35:06 moo apmd: resumed at 20010816 01:35:06 Aug 16 12:20:21 moo apmd[227]: apmevent 000b index 11 Aug 16 12:20:21 moo apmd[227]: apmevent 0002 index 12 Aug 16 12:20:22 moo apmd: suspend at 20010816 12:20:22 Aug 16 12:20:22 moo apmd: resumed at 20010816 12:20:22 Aug 16 13:25:12 moo apmd[227]: apmevent 0003 index 13 Aug 16 13:25:12 moo apmd: resumed at 20010816 13:25:12 Aug 16 13:26:48 moo apmd[227]: apmevent 0002 index 14 Aug 16 13:26:48 moo apmd: suspend at 20010816 13:26:48 Aug 16 13:27:31 moo apmd[227]: apmevent 0003 index 15 Aug 16 13:27:31 moo apmd[227]: apmevent 0002 index 16 Aug 16 13:27:31 moo apmd: resumed at 20010816 13:27:31 Aug 16 13:27:31 moo apmd: suspend at 20010816 13:27:31 Aug 16 13:27:57 moo apmd[227]: apmevent 0003 index 17 Aug 16 13:27:57 moo apmd: resumed at 20010816 13:27:57 Aug 16 14:02:19 moo apmd[265]: start i will wait for another spontaneous reboot before deciding to disable apm again. can anybody tell me what kind of messages should i be looking for related to the cause of system induced reboot? i didn't find anything _suspicious_ related to reboot in messages generated from kernel or amp(d). -- so, do you like word games or scrabble? - parv To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message