Subject: good news and bad news in PCMCIA and APM changes since 2001/03/24
To: NetBSD-current Discussion List <current-users@NetBSD.ORG>
From: Greg A. Woods <woods@weird.com>
List: current-users
Date: 06/29/2001 19:42:53
I just wanted to quickly report that there have been some apparently
good improvements in the PCMCIA and APM bits, at least on i386, since
the 2001/03/24 sources, and some not-so-good changes.

Below you'll see dmesg from one of the laptops I was having related
problems with up to this point.  The kernel is a slightly modified
GENERIC from 2001/06/24 sources, set up for X11 and PCMCIA (and some
more verbose messages).  You'll see that the APM driver no longer
continually spews the same message over and over but nicely stops
complaining after 10 events (it's still not terribly useful as the
suspend button still doesn't have a persistent effect, nor does apm
-z|-S have any effect).  You'll also see that both Megahertz PCMCIA
cards apparently probe properly now (the timeout on sm1 is because it's
not plugged into anything, but I have dhclient configured to try on all
interfaces).

Now the bad part.  I tried pulling both PC cards, and re-inserting the
X-jack one (which was sm2).  When I tried to re-run dhclient the machine
paniced.  So I rebooted and tried again, this time with just the one

	pcmcia1: card irq 5
	sm1: receive interrupt on empty fifo
	sm1: receive interrupt on empty fifo
	sm1: receive interrupt on empty fifo
	kernel: page fault trap, code=0
	Stopped at    sm91cxx_read+0x244:    repne insw    %dx,%es:(%edi)
	db> trace
	smc91cxx_read(c06f5400) at smc91cxx_read+0x244
	smc91cxx_intr(c06f5400) at smc91cxx_intr+0x125
	Xintr5() at Xintr5_0x78
	--- interrupt ---
	idle(c3fb3394) at idle+0x20
	bpendtsleep(c0580f0c,118,c0439fe4,0,0) at bpendtsleep
	sys_poll(c3fb3394,c4051f80,c4051f78) at sys_poll+0x21b
	syscall_plain(bfdf001f,805001f,1f,bfbf001f,bfbfdc20) at syscall_plain+0x98

So the end result is the machine still won't work without both Megahertz
cards installed -- it's just the failure mode that's different.  ;-)

Now it came up on the net the first time, but I've been having more
trouble since playing with the PC cards....  It just keeps complaining
"bogus UDP packet length: 351".


NetBSD 1.5W (GENERIC_LAPTOP) #13: Thu Jun 28 02:56:13 EDT 2001
    woods@proven:/backups/NetBSD-obj.i386/arch/i386/compile/GENERIC_LAPTOP
cpu0: Intel 486DX2 (486-class)
cpu0: features b<FPU,VME,PSE>
total memory = 20092 KB
avail memory = 13244 KB
using 276 buffers containing 1104 KB of memory
mainbus0 (root)
isa0 at mainbus0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
pckbc0 at isa0 port 0x60-0x64
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pmsattach: disable error
wdc0 at isa0 port 0x1f0-0x1f7 irq 14
wd0 at wdc0 channel 0 drive 0: <ST9655AG>
wd0: drive supports 16-sector PIO transfers, chs addressing
wd0: 500 MB, 1016 cyl, 16 head, 63 sec, 512 bytes/sect x 1024128 sectors
wd0: drive supports PIO mode 3, DMA mode 1
vga0 at isa0 port 0x3b0-0x3df iomem 0xa0000-0xbffff
wsdisplay0 at vga0: console (80x25, vt100 emulation), using wskbd0
lpt0 at isa0 port 0x378-0x37b irq 7
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
sysbeep0 at pcppi0
isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
npx0 at isa0 port 0xf0-0xff: using exception 16
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-0xdffff
pcic0: controller 0 (Cirrus PD672X) has sockets A and B
pcic0: controller 1 (Intel 82365SL Revision 1) has no sockets
pcmcia0 at pcic0 controller 0 socket 0
pcmcia1 at pcic0 controller 0 socket 1
isapnp0: no ISA Plug 'n Play devices found
apm0 at mainbus0: Power Management spec V1.2
apm: 0 batteries
apm0: A/C state: on
apm0: battery charge state:
apm0: estimated 0m
APM get event: unknown error code (0x530b)
biomask ef6d netmask ef6d ttymask ffef
pcic0: using irq 3 for socket events
APM get event: unknown error code (0x530b)
pcmcia0: CIS version PCMCIA 2.0 or 2.1
pcmcia0: CIS info: Megahertz, CC10BT/2, PCMCIA 10BASE-T/2 ETHERNET ADAPTER, 0000860595E2
pcmcia0: Manufacturer code 0x128, product 0x103
pcmcia0: function 0: network adapter, ccr addr 300 mask 1
pcmcia0: function 0, config table entry 1: I/O card; irq mask ffff; iomask 4, iospace 0-f; io8 io16 irqlevel
pcmcia0: function 0, config table entry 3: I/O card; irq mask ffff; iomask 5, iospace 0-1f; io8 io16 irqlevel
sm1 at pcmcia0 function 0APM get event: unknown error code (0x530b)
 port 0x400-0x40f: Megahertz X-JACK Ethernet
sm1: unknown chip id 15, revision 15, buffer size: 0
sm1: MAC address 00:00:86:05:95:e2, default media UTP
APM get event: unknown error code (0x530b)
pcmcia1: CIS version PCMCIA 2.0 or 2.1
pcmcia1: CIS info: Megahertz, CC10BT/2, PCMCIA 10BASE-T/2 ETHERNET ADAPTER, 0000861147E6
pcmcia1: Manufacturer code 0x128, product 0x103
pcmcia1: function 0: network adapter, ccr addr 300 mask 1
pcmcia1: function 0, config table entry 1: I/O card; irq mask ffff; iomask 4, iospace 0-f; io8 io16 irqlevel
pcmcia1: function 0, config table entry 3: I/O card; irq mask ffff; iomask 5, iospace 0-1f; io8 io16 irqlevel
sm2 at pcmcia1 function 0APM get event: unknown error code (0x530b)
 port 0x410-0x41f: Megahertz X-JACK Ethernet
sm2: SMC91C94, revision 1, buffer size: 4608
sm2: MAC address 00:00:86:11:47:e6, default media UTP
boot device: wd0
root on wd0a dumps on wd0b
APM get event: unknown error code (0x530b)
root file system type: ffs
APM get event: unknown error code (0x530b)
APM get event: unknown error code (0x530b)
APM get event: unknown error code (0x530b)
APM get event: unknown error code (0x530b)
APM get event: unknown error code (0x530b)
APM get event: unknown error code (0x530b)
apm: Last error 0x530b occurred 10 times; giving up.
pcmcia1: card irq 5
pcmcia0: card irq 9
sm1: device timeout
sm1: device timeout
sm1: device timeout
sm1: device timeout
sm1: device timeout
wsdisplay0: screen 1 added (80x50, vt100 emulation)
wsdisplay0: screen 2 added (80x50, vt100 emulation)
wsdisplay0: screen 3 added (80x50, vt100 emulation)
wsdisplay0: screen 4 added (80x50, vt100 emulation)
wsdisplay0: screen 5 added (80x50, vt100 emulation)
wsdisplay0: screen 6 added (80x50, vt100 emulation)
wsdisplay0: screen 7 added (80x50, vt100 emulation)
wsmux1: connecting to wsdisplay0
sm1: device timeout
sm1: device timeout
sm1: device timeout
sm1: device timeout
sm1: device timeout
sm1: device timeout

-- 
							Greg A. Woods

+1 416 218-0098      VE3TCP      <gwoods@acm.org>     <woods@robohack.ca>
Planix, Inc. <woods@planix.com>;   Secrets of the Weird <woods@weird.com>