From owner-freebsd-current Sun Aug 29 0: 0: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.ihug.co.nz (tk2.ihug.co.nz [203.29.160.14]) by hub.freebsd.org (Postfix) with ESMTP id 9127E14BEA for ; Sat, 28 Aug 1999 23:59:57 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (p16-max1.dun.ihug.co.nz [209.76.100.16]) by smtp2.ihug.co.nz (8.9.3/8.9.3/Debian/GNU) with ESMTP id SAA00531; Sun, 29 Aug 1999 18:58:25 +1200 Message-ID: <37C8DA0F.2F8A9D7A@es.co.nz> Date: Sun, 29 Aug 1999 18:58:23 +1200 From: Mike Muir X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mitsuru IWASAKI Cc: freebsd-current@FreeBSD.ORG Subject: Re: followup to apm problems. References: <37C3C2F4.DE91BB21@es.co.nz> <199908270647.PAA08317@tasogare.imasy.or.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mitsuru IWASAKI wrote: > OK. Probably `slept 00:00:00 - 00:00:40' problem was caused by PS/2 > mouse, I think. Do we need something to do with psm on suspending as > well as resuming? Im not sure anything needs to be done for PS/2.. check out these results.. > > > > ed1: irq 3 at device 9.0 on pci0 > Ahh, I meant just unplug cable tentatively to confirm. > # and uninstall NIC if possible :) > After the problem analyzed, we just try to fix it in proper place. Unplugged NIC, not diabled: Standby: Aug 29 18:33:44 pyros /kernel.old: APM ioctl: cmd = 0x2000500c Aug 29 18:36:28 pyros /kernel.old: Received APM Event: PMEV_STANDBYRESUME Aug 29 18:36:28 pyros /kernel.old: Execute APM hook "default resume." Aug 29 18:36:28 pyros /kernel.old: resumed from suspended mode (slept 00:02:42) Aug 29 18:36:28 pyros /kernel.old: Execute APM hook "PS/2 mouse." Aug 29 18:36:28 pyros /kernel.old: APM ioctl: cmd = 0x40284164 Aug 29 18:36:28 pyros /kernel.old: APM ioctl: cmd = 0x40284164 Aug 29 18:36:28 pyros apmd[355]: apmevent 000b index 3 Aug 29 18:36:28 pyros apmd: resumed at 19990829 18:36:28 Aug 29 18:36:28 pyros /kernel.old: APM ioctl: cmd = 0x40284164 And i pressed a key because i couldnt be biffed waiting any longer :) So it seems to be working properly! (Yes i am running apmd as well) Suspend: Aug 29 18:41:17 pyros /kernel.old: APM ioctl: cmd = 0x20005001 Aug 29 18:42:33 pyros /kernel.old: Execute APM hook "default suspend." Aug 29 18:42:33 pyros /kernel.old: Received APM Event: PMEV_NORMRESUME Aug 29 18:42:33 pyros /kernel.old: Execute APM hook "default resume." Aug 29 18:42:33 pyros /kernel.old: resumed from suspended mode (slept 00:01:15) Aug 29 18:42:33 pyros /kernel.old: Execute APM hook "PS/2 mouse." Aug 29 18:42:33 pyros /kernel.old: APM ioctl: cmd = 0x40284164 Aug 29 18:42:33 pyros /kernel.old: APM ioctl: cmd = 0x40284164 Aug 29 18:42:33 pyros apmd[355]: apmevent 0003 index 5 Aug 29 18:42:33 pyros apmd: resumed at 19990829 18:42:33 Aug 29 18:42:33 pyros /kernel.old: APM ioctl: cmd = 0x40284164 Same deal, I resumed it manually - so it seems to be working also. > At least, apm is in /usr/sbin/, apm -z touches /dev/apm and apmd > writes log on /var/log/ via syslog :) > Using `sysctl -w machdep.apm_suspend_delay=30 (or enough time for > spinning down)' and moving `camcontrol stop' to the end of command > list would be success. Otherwise, please forgive me. :) I tried that and the drive spins down, and right about 5 seconds before the 30 seconds is up, it spins back up again by itself, then it goes into suspend, but then comes right back out (presumably because of the disk activity). P.S plugging it back in, i do notice it resumes whenever there is activity on the hub :D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message