----Next_Part(Tue_Nov_18_16:27:14_1997)--
Content-Type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

I am having problems getting APM to work on my laptop (a Dell
Latitude XPi/CD 150), and I would like to know:

 o Is the APM code considered to be stable and/or usable in
   1.3_ALPHA?

 o Is anyone else than me seeing the symptoms I do?

My problem is that I appear unable to get the suspend function to
work as it should.  I have turned on full debugging in apm.c, and
this is what happens:

During autoconf, I get the messages as shown below in the
attachment.  After autoconf it continues on with printing
messages "apmcall: func 11 from line 509 -> 0x1" about once per
second.

If I log in and do "zzz", I get "Suspending system..." and the
following debug lines:

apmcall: func 11 from line 509 -> 0x1
apmcall: func 10 from line 676 -> 0x0
apmcall: func 11 from line 509 -> 0x1
apmcall: func 11 from line 509 -> 0x1
apmcall: func  7 from line 604

and the cursor just sits behind the "604".  The bell "beeps" at
the same time the last line is printed, but the screen is still
on, and the power indicator on the PC is also on, but at this
point the PC appears to be completely wedged, so I need to power
cycle it to get its attention back.

If I press the "suspend" function key, the behaviour is a little
different, I get:

apmcall func 11 from line 509 -> 0x1
apmcall func 11 from line 509 -> 0x0
apmev: user suspend request
apmcall func  7 from line 604 -> 0x0
apmcall func 11 from line 509 -> 0x1
apmcall func  7 from line 604 -> 0x0
apmcall func 11 from line 509 -> 0x1
apmcall func  7 from line 604 -> 0x0
apmcall func 11 from line 509 -> 0x1
apmcall func  7 from line 604

and it freezes (as above) at this point.

If I try to close the lid of the PC, the same thing appears to
happen, the bell beeps but the power light remains on (when the
PC suspends properly, the power light goes into a "short blink
once in a while" mode instead).  However, when I open the lid to
look at the debug messages, the screen light has been turned off,
so I can't really tell what happened...

About 6 months ago (?) I used to run NetBSD on this laptop with
John Kohl's old PCMCIA patches and the then built-in APM support
(I think it was integrated at that time), and I remember APM as
working Just Fine on this machine with NetBSD.

Any help would be appreciated.


Regards,

- H=E5vard

----Next_Part(Tue_Nov_18_16:27:14_1997)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

(start dropped from kernel message buffer, but this is mostly
complete...)

/i386/compile/XPI
cpu0: family 5 model 2 step c
cpu0: Intel Pentium (P54C) (586-class)
real mem  = 49934336
avail mem = 44822528
using 635 buffers containing 2600960 bytes of memory
biostramp installed @ 1000
mainbus0 (root)
pci0 at mainbus0 bus 0: configuration mode 1
Picopower Technology product 0x0001 (host bridge, revision 0x04) at pci0 dev 0 function 0 not configured
Picopower Technology product 0x8002 (ISA bridge) at pci0 dev 6 function 0 not configured
Neomagic product 0x0002 (VGA display, revision 0x01) at pci0 dev 7 function 0 not configured
CMD Technology product 0x0643 (IDE mass storage, interface 0x80) at pci0 dev 8 function 0 not configured
Texas Instruments PCI1130 (CardBus bridge, revision 0x04) at pci0 dev 9 function 0 not configured
Texas Instruments PCI1130 (CardBus bridge, revision 0x04) at pci0 dev 9 function 1 not configured
isa0 at mainbus0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
wdc0 at isa0 port 0x1f0-0x1f7 irq 14
atapibus0 at wdc0
wd0 at wdc0 drive 0: <IBM-DCRA-22160>
wd0: 2067MB, 4200 cyl, 16 head, 63 sec, 512 bytes/sec
wd0: using 16-sector 16-bit pio transfers, lba addressing
wdc1 at isa0 port 0x170-0x177 irq 15
atapibus1 at wdc1
cd0 at atapibus1 drive 0: <CD-ROM  CDR-N16D, , 1.40> type 5 cdrom removable
npx0 at isa0 port 0xf0-0xff: using exception 16
pc0 at isa0 port 0x60-0x6f irq 1: color
pms0 at pc0 irq 12
pc0: console
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
pcic0 at isa0 port 0x3e0-0x3e1 iomem 0xd0000-0xd3fff: using irq 3
pcic0: controller 0 (Intel 82365SL Revision 1) has sockets A and B
pcmcia0 at pcic0 controller 0 socket 0
com1 at pcmcia0 function 0 port 0x2f8-0x2ff: ns16550a, working fifo
pcmcia0: card irq 5
pcmcia1 at pcic0 controller 0 socket 1
ep0 at pcmcia1 function 0 port 0x330-0x33f: 3Com 3C589 Ethernet
ep0: MAC address 00:20:af:85:6a:ab
ep0: 8KB byte-wide FIFO, 5:3 Rx:Tx split, utp/aui/bnc (default utp)
apm: bioscall return: 102 504d 3 0 a92<OVFL,IEN,NF,AF> 0 0
apm0 at mainbus0: bioscall return: 102 504d 3 0 a92<OVFL,IEN,NF,AF> 0 0
apm0: bioscall return: 304 0 0 0 a97<OVFL,IEN,NF,AF,PF,CY> 0 0
apm0: bioscall return: f000 f0fc f000 f000 206<IEN,PF> ffff ffff
apm0: data segment fine: [f0000,fffff)
apm0: code32len=ffff, datalen=ffff
apm0: detail 30102 32b:f0000/0xf02b5000/ffff 16b:f0000/0xf02b5000 data f0000/0xf02b5000/ffff ep f0fc (30:0xf02c40fc) 0xf0200690
apm0: apmcall: func 14 from line 645 -> 0x0
Power Management spec V1.1
apmcall: func 15 from line 567 -> 0x0
apmcall: func 10 from line 676 -> 0x0
apm0: battery life expectancy: 92%
apm0: A/C state: on
apm0: battery charge state: high charging
apm0: estimated 4h 0m
apmcall: func 11 from line 509 -> 0x1
biomask c040 netmask c040 ttymask d04a

----Next_Part(Tue_Nov_18_16:27:14_1997)----