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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
