From owner-freebsd-current  Sat Aug 21 12: 9:44 1999
Delivered-To: freebsd-current@freebsd.org
Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5])
	by hub.freebsd.org (Postfix) with ESMTP id DAF1214C84
	for <freebsd-current@freebsd.org>; Sat, 21 Aug 1999 12:09:37 -0700 (PDT)
	(envelope-from iwasaki@jp.FreeBSD.org)
Received: from localhost (isdn35.imasy.or.jp [202.227.24.227])
	by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id EAA24374;
	Sun, 22 Aug 1999 04:08:39 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Message-Id: <199908211908.EAA24374@tasogare.imasy.or.jp>
To: kfarmer@sympatico.ca
Cc: iwasaki@jp.FreeBSD.org, freebsd-current@freebsd.org
Subject: Re: apm problems.
In-Reply-To: Your message of "Tue, 17 Aug 1999 04:56:47 +0000"
	<37B8EB8F.F7DA55B1@sympatico.ca>
References: <37B8EB8F.F7DA55B1@sympatico.ca>
X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Sun, 22 Aug 1999 04:12:09 +0900
From: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
X-Dispatcher: imput version 980905(IM100)
Lines: 58
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi, sorry to late.

> > 1. Standby by PM timer in BIOS setting fails with the system activity.
> 
> If by fails you mean enters standby mode, then yes the computer enters
> standby mode while the system is active, after the period of time set in
> the bios, as long as no keys have been pressed on the keyboard during
> that time.

Ah, If you want to reject the standby request from BIOS while the
system is active, then apmd would be useful. You can configure it like
this:
in /etc/apmd.conf:
apm_event PMEV_STANDBYREQ {
	reject;
}

or

apm_event PMEV_STANDBYREQ {
	exec "/etc/rc.standby_with_system_activity";
}

with /etc/rc.standby_with_system_activity:
#!/bin/sh
if [ some_script_to_check_system_is_active ]
then
	# apmd will reject the event...
	exit 1
fi

> > 2. No new process can be started after resume.
> > Is it correct?
> 
> Yes, although this doesn't happen every time, sometimes everything is ok
> after a resume.
> This seems to be very repeatable following these steps.
> 
> cd /usr/bin
> cp * /tmp &
> sleep 1 && apm -z (while copy is still in progress)
> [hit a key]
> any new process started freezes, nothing happens (including logins in
> getty, halt etc).

I tried these steps many times, but I couldn't see the problem.
I guess your disks are still in a SLEEP after a resume or 
I/O interrupts were lost during suspend/resume or something.
Anyone suggestions?

> ata0: master: setting up WDMA2 mode on PIIX3/4 chip OK
> ad0: <QUANTUM FIREBALL_TM1280A/A6B.2D00> ATA-? disk at ata0 as master
> ad0: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S
> ad0: piomode=4, dmamode=2, udmamode=-1
> ad0: 16 secs/int, 0 depth queue, DMA mode

If your problem is related with disks, have you tried wd device driver
instead of ata?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message