From owner-freebsd-mobile Wed Oct 29 17:48:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA03586 for mobile-outgoing; Wed, 29 Oct 1997 17:48:49 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA03566 for ; Wed, 29 Oct 1997 17:48:39 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.7) with ESMTP id RAA03943; Wed, 29 Oct 1997 17:48:34 -0800 (PST) (envelope-from jdp) Message-Id: <199710300148.RAA03943@austin.polstra.com> To: Nate Williams cc: mobile@freebsd.org Subject: Re: Suspend/resume in -current: still no joy In-reply-to: Your message of "Wed, 29 Oct 1997 16:57:00 MST." <199710292357.QAA14798@rocky.mt.sri.com> Date: Wed, 29 Oct 1997 17:48:33 -0800 From: John Polstra Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Oooh, I've got a big clue! But first ... > > 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? OK, I tried. And I want you to be fully aware of the extreme personal cost at which I did that. Because every time I have to interact with Windows 95, I damn near have a stroke. This exercise probably took 2 years off my life span. Anyway, in Windows 95 I found a couple of places where you could enable/disable waking up the machine on an incoming call. Both were already disabled. Back in Unix again (whew!), I made it fail again. I did that by "apmconf -e" followed by "zzz". It resumed all by itself right away, though it didn't seem to hang this time. Here are the messages it produced: sio2: unload,gone Return IRQ=10 Slot 0, unfielded interrupt (0) Card disabled, slot 0 resumed from suspended mode (slept 00:00:01) Card inserted, slot 0 Entire system suspend failure: errcode = 96 Now here's the clue. I can make it fail like that reliably when the AC adapter is plugged in. But if I unhook the AC so that it's using battery power, suspend/resume works perfectly every time! Plug in the AC, and it fails again. Unplug it, and it works again. What do you think about that? :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth