Date: Sun, 23 Jan 2000 00:24:52 +0100 From: Jesper Skriver <jesper@skriver.dk> To: current@FreeBSD.ORG Subject: Re: apm suspend ?? Message-ID: <20000123002452.A20926@skriver.dk> In-Reply-To: <20000119001306.A74876@skriver.dk>; from jesper@skriver.dk on Wed, Jan 19, 2000 at 12:13:06AM %2B0100 References: <20000116205650.A64495@skriver.dk> <200001171818.LAA10403@harmony.village.org> <20000117212038.A69519@skriver.dk> <20000117170014.A22939@netmonger.net> <20000117234623.A70090@skriver.dk> <20000119001306.A74876@skriver.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 19, 2000 at 12:13:06AM +0100, Jesper Skriver wrote: > On Mon, Jan 17, 2000 at 11:46:23PM +0100, Jesper Skriver wrote: > > On Mon, Jan 17, 2000 at 05:00:14PM -0500, Christopher Masto wrote: > > > On Mon, Jan 17, 2000 at 09:20:38PM +0100, Jesper Skriver wrote: > > > > On Mon, Jan 17, 2000 at 11:18:02AM -0700, Warner Losh wrote: > > > > > In message <20000116205650.A64495@skriver.dk> Jesper Skriver writes: > > > > > : Just upgraded my laptop from a Jan 5th -CURRENT to todays, and now > > > > > : suspend doesn't work as expected. > > > > > : > > > > > : When I run 'apm -z' the laptop suspends as normal, but right after this > > > > > : the harddisk led turns on, and it powers up again. > > > > > > > > > > That's very odd. apm hasn't changed since Dec 2 and even that was > > > > > just deleting code that had been obsolete for a while now. > > > > > > > > I don't get it either - will try to revert to -CURRENT as of jan 5th, > > > > and see if it works again ... > > > > > > Sometimes the "enter" at the end of the command is sufficient to wake the > > > machine back up. Have you tried "sleep 2; apm -z"? > > > > Yep, that's not it. > > > > I've just verified, by reverting to -CURRENT as of > > *default date=2000.01.05.12.00.00 > > > > Suspend works as expected, tomorrow I'll try at 2 days intervals, to try > > to narrow down the commit making the difference ... > > And it also works as of > > *default date=2000.01.13.23.00.00 > > But didn't on the cvsup on the 16th ... will try to narrow it down even > further ... I've been trying to narrow it down as much as possible, but -CURRENT was very broken around this time ... *default date=2000.01.05.12.00.00 builds - and suspend works *default date=2000.01.13.23.00.00 builds - and suspend works *default date=2000.01.14.03.00.00 cannot build *default date=2000.01.14.06.00.00 cannot build *default date=2000.01.14.12.00.00 cannot build *default date=2000.01.15.03.00.00 cannot build *default date=2000.01.15.23.00.00 cannot build *default date=2000.01.16.08.00.00 cannot build *default date=2000.01.16.18.00.00 cannot build *default date=2000.01.17.02.00.00 cannot build *default date=2000.01.17.13.00.00 cannot build *default date=2000.01.17.23.00.00 cannot build *default date=2000.01.18.22.00.00 builds - but suspend doesn't work Does anyone have any ideas, on what happened, that made suspend not work ? To summarize, it suspends fine, but immediate power-up again ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE# 5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000123002452.A20926>