Date: Fri, 4 May 2001 14:39:12 +0200 From: "Georg-W. Koltermann" <gwk@sgi.com> To: Dag-Erling Smorgrav <des@ofug.org> Cc: current@freebsd.org, David Wolfskill <david@catwhisker.org> Subject: Re: lockup after resume Message-ID: <20010504143910.B11325@hunter.munich.sgi.com> In-Reply-To: <xzpvgoetp41.fsf@flood.ping.uio.no>; from des@ofug.org on Mon, Apr 09, 2001 at 11:10:54AM %2B0200 References: <20010328212426.A32322@hunter.munich.sgi.com> <xzpvgoetp41.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 09, 2001 at 11:10:54AM +0200, Dag-Erling Smorgrav wrote: > "Georg-W. Koltermann" <gwk@sgi.com> writes: > > I am experiencing a strange lockup with -current as of about a week > > ago: It will suspend and resume, but after the resume the console is > > dead and the system hangs after a short while. > > I'm seeing this too on my laptop. Used to work fine, no longer does. > I'll try the latest & greatest and see if the problem goes away. > > DES Dag-Erling, I CVSuped twice since my initial report, and the problem is still there. On the other hand I have a report from David Wolfskill that suspend/resume works fine for him. a) Does suspend/resume now work for you? b) What hardware/firmware do you have (mine is a DELL Inspiron 7500 with BIOS rev A12)? c) David, since it seems to work for you, what hardware/firmware do you have? 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. -- Regards, Georg. ---------------------------------------------------------------------- Who in the world needs 2000 Windows? 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?20010504143910.B11325>