Re: apm problems.

[Kelvin Farmer]

Mitsuru IWASAKI wrote:

> 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;

Thanks.


> 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:  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?

wdc0 at port 0x1f0-0x1f7 irq 14 on isa0
wdc0: unit 0 (wd0): 
wd0: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S
wdc0: unit 1 (atapi): , removable, accel, dma,
iordis
wcd0: drive speed 1378KB/sec, 128KB cache
wcd0: supported read types: CD-R, CD-DA
wcd0: Audio: play, 256 volume levels
wcd0: Mechanism: ejectable tray
wcd0: Medium: no/blank disc inside, unlocked
wdc1 at port 0x170-0x177 irq 15 on isa0
wdc1: unit 0 (wd2): 
wd2: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S 

now, after resuming from apm -z, theres a pause then the message:

wd2: interrupt timeout (status 58 )
wd2: timeout () DMA status 4

and things seem to work ok again.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: apm problems.

[Mitsuru IWASAKI]

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:  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

Re: apm problems.

[Kelvin Farmer]

> Hi,
>
> My understanding on your problems is:
> 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.

> 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).

> 1. My laptops also fails if the console or window is updating by the
>output from running commands.  But standby on other unused console
>(ttyv1 or something), monitor blanks.  Standby usually never stop
>disk activities.

> 2. Do you have `calcru: negative time' messages after resume?  One of

No. 

>Another possibility is apmd configuration.  Is it correctly configured?
>Please try to disable apmd to make it clear whether apmd causes
>your problem.

It does not appear to be apmd causing the problem since it occurs
without apmd running.

> > Apm does not seem to be behaving correctly on my computer (running
> > yesterday's CURRENT)
> 
> Is this first time for you?  Have you met the problems before or just
> recently?

I just recently enabled apm & apmd, I had the problem of it going to
standby mode while the system was busy awhile ago so disabled apm,
however the problem of not being able to start new process is new.


> I'd like to have your dmesg output.  Are you using desktop PC, right?

Yes, this is a desktop PC.

Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights
reserved.
FreeBSD 4.0-CURRENT #1: Mon Aug 16 21:14:53 EDT 1999
[EMAIL PROTECTED]:/usr/src/sys/compile/TRISTAL
Timecounter "i8254"  frequency 1193343 Hz
CPU: AMD-K6tm w/ multimedia extensions (199.93-MHz 586-class CPU)
  Origin = "AuthenticAMD"  Id = 0x562  Stepping = 2
  Features=0x8001bf
  AMD Features=0x400<>
real memory  = 67108864 (65536K bytes)
avail memory = 62623744 (61156K bytes)
Preloaded elf kernel "kernel" at 0xc0268000.
Probing for PnP devices:
CSN 1 Vendor ID: CTL0070 [0x70008c0e] Serial 0x Comp ID: PNPb02f
[0x2fb0d041]
Add hook "pcm resume handler"
Add hook "pcm suspend handler"
pcm1 (SB16pnp  sn 0x) at 0x220-0x22f irq 5 drq 1 flags
0x15 on isa
npx0:  on motherboard
npx0: INT 16 interface
apm0:  on motherboard
apm: APM BIOS version 0102
apm: Code16 0xc00f, Data 0xc400
apm: Code entry 0xef50, Idling CPU disabled, Management enabled
apm: CS_limit=0x, DS_limit=0x
apm: Engaged control enabled
apm: found APM BIOS v1.2, connected at v1.2
apm: Slow Idling CPU disabled
Add hook "default suspend"
Add hook "default resume"
pcib0:  on motherboard
pci0:  on pcib0
isab0:  at device 7.0 on pci0
ata-pci0:  at device 7.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0
vga-pci0:  irq 11 at device 20.0 on
pci0
isa0:  on motherboard
fdc0:  at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0:  at port 0x60-0x6f on isa0
atkbd0:  irq 1 on atkbdc0
sc0:  on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
vga0:  at port 0x3b0-0x3df iomem 0xa-0xb on
isa0
sio0 at port 0x3f8-0x3ff irq 4 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0 at port 0x378-0x37f irq 7 on isa0
ppc0: PC87306 chipset (PS2/NIBBLE) in COMPATIBLE mode
lpt0:  on ppbus 0
lpt0: Interrupt-driven port
ata0: master: setting up WDMA2 mode on PIIX3/4 chip OK
ad0:  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
ata1: master: setting up WDMA2 mode on PIIX3/4 chip OK
ad1:  ATA-3 disk at ata1 as master
ad1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S
ad1: piomode=4, dmamode=2, udmamode=2
ad1: 16 secs/int, 0 depth queue, DMA mode
atapi: piomode=3, dmamode=-1, udmamode=-1
atapi: PIO transfer mode set
acd0:  CDROM drive at ata0 as slave
acd0: drive speed 1378KB/sec, 128KB cache
acd0: supported read types: CD-R, CD-DA  
acd0: Audio: play, 256 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: no/blank disc inside, unlocked
changing root device to wd1s1a
APM ioctl: cmd = 0x20005005
called apm_event_enable()
apmwrite: event 0x2 enabled
apmwrite: event 0x3 enabled
apmwrite: event 0xa enabled
apmwrite: event 0xb enabled


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: apm problems.

[Mitsuru IWASAKI]

Hi,

My understanding on your problems is:
1. Standby by PM timer in BIOS setting fails with the system activity.
2. No new process can be started after resume.
Is it correct?

1. My laptops also fails if the console or window is updating by the
   output from running commands.  But standby on other unused console
   (ttyv1 or something), monitor blanks.  Standby usually never stop 
   disk activities.

2. Do you have `calcru: negative time' messages after resume?  One of
   my laptops has this problem, doesn't restore the countdown register of
   i8254 on resume.  After resume, my laptop is getting very slooow,
   takes 2 mins to shutdown...  If your problem is the same as mine,
   hack in PAO (i8254_restore() in /sys/i386/apm/apm.c and
   /sys/i386/isa/clock.c) would be helpful for you.
   Another possibility is apmd configuration.  Is it correctly configured?
   Please try to disable apmd to make it clear whether apmd causes
   your problem.

> Apm does not seem to be behaving correctly on my computer (running
> yesterday's CURRENT)

Is this first time for you?  Have you met the problems before or just
recently?

> if more info is needed, just let me know what to do. Thanks =).

I'd like to have your dmesg output.  Are you using desktop PC, right?



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message