From owner-freebsd-current Fri May 4 7:57:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 860ED37B43F for ; Fri, 4 May 2001 07:57:33 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id QAA34831; Fri, 4 May 2001 16:57:19 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Georg-W. Koltermann" Cc: current@freebsd.org, David Wolfskill Subject: Re: lockup after resume References: <20010328212426.A32322@hunter.munich.sgi.com> <20010504143910.B11325@hunter.munich.sgi.com> From: Dag-Erling Smorgrav Date: 04 May 2001 16:57:19 +0200 In-Reply-To: <20010504143910.B11325@hunter.munich.sgi.com> Message-ID: Lines: 25 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Georg-W. Koltermann" writes: > a) Does suspend/resume now work for you? No, but I haven't upgraded my kernel since right before Easter. > b) What hardware/firmware do you have (mine is a DELL Inspiron 7500 > with BIOS rev A12)? IBM ThinkPad 600E, don't remember the firmware revision but it's very recent. > One surprising observation: If I disable APM in /boot/device.hints, my > machine suspends and resumes JUST FINE. The BIOS alone seems to be > able to suspend and awake the hardware behind FreeBSD's back. The > system only hangs if FreeBSD is involved in the process. Hmm, I might try that. BTW, last time I asked Warner about this his reply was (I paraphrase) "it's not supposed to work, and if it ever worked for you it was out of sheer luck", which I find surprising. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message