From owner-freebsd-mobile Wed Oct 29 15:57:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA26172 for mobile-outgoing; Wed, 29 Oct 1997 15:57:10 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA26167 for ; Wed, 29 Oct 1997 15:57:04 -0800 (PST) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id QAA05254; Wed, 29 Oct 1997 16:57:01 -0700 (MST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA14798; Wed, 29 Oct 1997 16:57:00 -0700 (MST) Date: Wed, 29 Oct 1997 16:57:00 -0700 (MST) Message-Id: <199710292357.QAA14798@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: John Polstra Cc: Nate Williams , mobile@freebsd.org Subject: Re: Suspend/resume in -current: still no joy In-Reply-To: <199710292353.PAA03250@austin.polstra.com> References: <199710291919.MAA13105@rocky.mt.sri.com> <199710292353.PAA03250@austin.polstra.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > OK. :-) Here's something else to think about. Sometimes it looks as > though the machine has started to suspend, but then gets yanked back > to life. Once I watched it almost-suspend for maybe 10 seconds before > hearing the disk spin up again all by itself. (I say "almost" suspend > because I'm pretty sure the suspend light never came on.) OK. > What I'm getting at is this: The manual for the ThinkPad 560 says > that an incoming call on the modem can wake up the machine when it is > in the suspended state. I'm having problems only with the modem card, > not with the ethernet card. On most machines, this can be disabled in the BIOS. (I think you can get to it in Win95). Can you try disabling it? > Could it be that the card is emitting a > spurious indication of an incoming call, due to some error in the way > it's being shut down? Sure, then the APM bios won't allow it to shut down, and we have all sorts of weirdness going on. Error handling from un-successful attempts are currently pretty weak. Nate