From owner-freebsd-current Fri Apr 23 13:48: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (Postfix) with ESMTP id 8FED81550C for ; Fri, 23 Apr 1999 13:48:03 -0700 (PDT) (envelope-from plm@smtp1.xs4all.nl) Received: from localhost. (dc2-isdn1998.dial.xs4all.nl [194.109.155.206]) by smtp1.xs4all.nl (8.8.8/8.8.8) with ESMTP id WAA25714 for ; Fri, 23 Apr 1999 22:45:29 +0200 (CEST) Received: (from plm@localhost) by localhost. (8.9.3/8.9.1) id WAA00567; Fri, 23 Apr 1999 22:45:29 +0200 (MET DST) (envelope-from plm) To: freebsd-current@freebsd.org Subject: suspend mode broken since one week ago From: Peter Mutsaers Date: 23 Apr 1999 22:22:51 +0200 Message-ID: <87so9r3x44.fsf@muon.xs4all.nl> X-Mailer: Gnus v5.6.45/Emacs 20.3 Lines: 22 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I rebuilt my kernel just after the new config stuff (nexus). Since then (but I'm not 100% sure it is related to this) my desktop computer doesn't suspend anymore. Before that, I could suspend it either by: - pressing the suspend button - zzz command (apm -z) - wait until BIOS-set time for suspend mode passes Now it won't suspend in any way anymore (which is irritating since my computer is in the living room; it must be quiet but I don't want it to reboot all the time). Is this a bug that I should report through send-pr, is it already known as a bug or is this an intentional change in behaviour? -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know plm@xs4all.nl | the Netherlands | what I'm doing. ---------------+---------------------+------------------ Running FreeBSD-current UNIX. See http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message