Use this page to discuss PCMCIA power management and APM issues. Before posting, be sure you've checked any relevant sections of the PCMCIA-HOWTO, such as: Particularly useful bits of information to post include your laptop's make and model; the type(s) of card(s) you are using; your linux distribution; and, of course, any relevant system log messages.

Messages Inline: [ 0 ]  [ All ]  Outline: [ 1 ]  [ 2 ]  [ All ] 

Sad: no data flows following suspend on Vaio PCG-N505VE

Date: 1999, Dec 15
From: Barak Pearlmutter bpearlmutter

On my Sony VAIO PCG-N505VE, PCMCIA works fine until the machine is suspended. Upon resume everything seems fine, but no data flows. Cards are sensed properly, the network is set up, the power lights come on. Then no data actually flows. This occurs with all cards I've trie, both pcmcia and cardbus, and with all versions of the drivers up to 3.1.5. The one exception was a modem card, which almost worked after the resume, but at an extraordinarily low data rate, eg a minute to echo each character.

With a cardbus Linksys 10/100 ethernet card, this message appears in this no-data-flowing state: 

  eth0: Tx hung, 11 vs. 0.

The only cure seems to be a reboot - unloading a reloading the pcmcia subsystem doesn't help.

Some probably irrelevant information:

$ dmesg 

PnP: PNP BIOS installation structure at 0xc00f6db0
PnP: PNP BIOS version 1.0, entry at f0000:b358, dseg at 400
PCI routing table version 1.0 at 0xfdf60
Intel PCIC probe: 
  Ricoh RL5C475 PCI-to-CardBus at bus 0 slot 12, mem 0x68000000, 1 socket
    host opts [0]: [serial irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat 168/176] [bus 32/34]
    ISA irqs (default) = 10,11,15 polling interval = 1000 ms
cs: IO port probe 0x1000-0x17ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x330-0x337 0x370-0x37f 0x388-0x38f
cs: IO port probe 0x0a00-0x0aff: clean.
cs: cb_alloc(bus 32): vendor 0x1011, device 0x0019
cs: cb_config(bus 32)
  fn 0 bar 1: io 0x280-0x2ff
  fn 0 bar 2: mem 0x600c0000-0x600c03ff
  fn 0 rom: mem 0x60080000-0x600bffff
cs: cb_enable(bus 32)
  bridge io map 0 (flags 0x21): 0x280-0x2ff
  bridge mem map 0 (flags 0x1): 0x60080000-0x600c0fff
tulip_attach(bus 32, function 0)
tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
eth0: Digital DS21143 Tulip rev 65 at 0x280, 00:E0:98:09:9E:F1, IRQ 10.
eth0:  EEPROM default media type Autosense.
eth0:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
eth0:  MII transceiver #0 config 3000 status 7809 advertising 01e1.

$ cardctl status 

Socket 0:
  3.3V CardBus card
  function 0: [ready]

$ lsmod

Module Size Used by tulip_cb 30388 2 cb_enabler 2284 2 [tulip_cb] ds 7040 1 [cb_enabler] i82365 30652 1 pcmcia_core 52816 0 [cb_enabler ds i82365] sb 31924 1 (autoclean) uart401 5628 1 (autoclean) [sb] sound 55116 0 (autoclean) [sb uart401] soundcore 2204 6 (autoclean) [sb sound]

$ cat /proc/pci 

  Bus  0, device  12, function  0:
    CardBus bridge: Ricoh Unknown device (rev 128).
      Vendor id=1180. Device id=475.
      Medium devsel.  Master Capable.  Latency=168.  Min Gnt=128.Max Lat=7.

$ uname -a

Linux sonyboy 2.2.13 #1 Wed Nov 17 12:00:40 MST 1999 i686 unknown

$ cat /proc/bus/pccard/00/info

type: Ricoh RL5C475 psock: 0 bus: 00 devfn: 0c.0 cardbus: 20

1. Looks like interrupts have been switched off by David Hinds, 1999, Dec 15
1. Re: Looks like interrupts have been switched off by Barak Pearlmutter, 1999, Dec 16
(_ Re: Looks like interrupts have been switched off by Barak Pearlmutter, 1999, Dec 17
(_ Feedback: Re: Looks like interrupts have been switched off by Martin Sillence, 1999, Dec 20
2. Ok: Untitled by Martin Sillence, 2000, Mar 15

Sad: aha152x_cs and apm -suspend

Date: 2000, Jan 10
From: Christian Gennerat c_gennerat

aha152x_cs and apm -suspend (with CD.rom Vendor:RICOH Model:MP6200S Rev:2.03)

/etc/pcmcia/scsi

Now, the command scsi_info is executed for all commands. After a suspend/resume, scsi_info, which includes an open of the scsi device, waits about 6 minutes before any reply.

I suggest to move (and duplicate) the following group into each branch where it is needed, i.e: start, stop, and cksum. 

    # get SCSI_ID
    eval `/sbin/scsi_info /dev/$DEVICE` || usage
    ADDRESS="$SCHEME,$TYPE,$SOCKET,$SCSI_ID"
    . $0.opts

After a suspend/resume, the scsi device is not operationnal, I must execute a 'cardctl eject' which takes about 6 minutes, if no running task is using the mounted filesystem /cdrom, and then 'cardctl insert', and all is fine.

Obviously, when I do not forget to unmount /cdrom and stop the scsi device with 'cardctl eject', it is still better!

Sad: Card not recognised when on battery power on Toshiba laptop

Date: 2000, Feb 19
From: Brian Mays brian

Card not recognised when on battery power on Toshiba laptop

I have a Xircom REM56G Ethernet/modem combo running on a Toshiba 490CDT laptop. The card is recognised and works without problems when the laptop is running on AC power.

The entry in /var/log/daemon.log looks like: 

    Feb  2 13:57:29 strider cardmgr[1566]: initializing socket 0
    Feb  2 13:57:29 strider cardmgr[1566]: socket 0: Xircom CEM56 Ethernet/Modem
    Feb  2 13:57:29 strider cardmgr[1566]: executing: 'insmod /lib/modules/2.2.14/pcmcia/xirc2ps_cs.o'
    Feb  2 13:57:29 strider cardmgr[1566]: executing: 'insmod /lib/modules/2.2.14/pcmcia/serial_cs.o'
    Feb  2 13:57:32 strider cardmgr[1566]: executing: './network start eth0'
    Feb  2 13:57:34 strider cardmgr[1566]: executing: './serial start ttyS3'

However, I find that when I am running on battery power, and try to reinsert the card (to get the network going after a suspend/resume cycle, say), it gets misinterpreted as "anonymous memory", with the corresponding entry in daemon.log being 

    Feb  2 13:52:46 strider cardmgr[1429]: initializing socket 0
    Feb  2 13:52:46 strider cardmgr[1429]: socket 0: Anonymous Memory
    Feb  2 13:52:46 strider cardmgr[1429]: executing: 'insmod /lib/modules/2.2.14/pcmcia/memory_cs.o'
    Feb  2 13:52:46 strider cardmgr[1429]: executing: './memory start mem0'

To get the card working properly under these conditions, I have to manually restart pcmcia (/etc/init.d/pcmcia restart), and then the card will be recognised on the next insertion (but not upon reinsertion after that).

The PCMCIA-HOWTO mentions some techniques for overcoming the "anonymous memory" problem, restricting the memory range scanned or setting speed options, but in my case they did not seem to help. It's possible I just didn't tweak them the right way, but it seems to me those suggestions really apply only if you *always* get the "anonymous memory" problem, whereas I only get it under battery power (and with certain BIOS settings, see following).

This problem may possibly be restricted to Toshiba laptops, and I have found a way of getting around the problem, allowing for reinsertion of the card under battery power without restarting pcmcia-cs, by changing BIOS settings. The Toshiba BIOS has an entry defining the way the PCMCIA slots are handled. There are 3 alternatives: default "automatic", which chooses between the other two which are "PCIC compatible" and "Cardbus/16bit".

I find that if I set the BIOS to "PCIC compatible", then my card (a 16bit PCMCIA card) is recognised perfectly, even under battery power. Problem solved, so to speak. If however I set it to either "automatic" or "Cardbus/16bit", then I get the problem I've been describing.

This suggests to me there is a bug in the cardbus code, which induces the problem when you're operating under battery power. I don't have a cardbus card so I can live with setting the BIOS to "PCIC", but it seemed worth reporting for the sake of others.

This problem is known to exist with version 3.1.8 and 3.1.10 of PC Card Services.

1. Oh well; I thought this was fixed in 3.1.3 by David Hinds, 2000, Feb 21

Question: linux-2.3.47 (and earlier)

Date: 2000, Feb 24
From: Lutz <urc8@rz.DO_NOT_SPAM_ME.uni-karlsruhe.de>

linux-2.3.47 is not the first kernel to freeze when trying to suspend my laptop. It began somewhat after 2.3.28. However, I now know that the reason has to be pcmcia. The system freezes exactly at this point when booting: 

(...)
Linux PCMCIA CardServices 3.1.11
  options:  [pci] [cardbus] [apm]
Adding cardbus controller 0: Texas Instruments PCI1131
PCI: Assigned IRQ 9 to device 00:0a.0 [PIIX-NEW]

Here, the system freezes (when playing around with apm). Is someone working on this problem? I would like to move to some kernels later than 2.3.28 :-)

Thanks!

Lutz

Ok: Success with suspend/resume between networks

Date: 2000, May 14
From: Steinar Bang sb

I am moving my linux laptop between three locations: two LANs at work, and my home LAN, connected to the internet via a cable modem.

The laptop is a Dell Inspiron 3500, and the linux installation started out as SuSE 6.2 (with ISC dhclient as the DHCP client).

Ever since I got my laptop, and rebuilt the kernel (2.2.10) to have APM suppord, I have used suspend/resume rather than shutdown and reboot when moving between networks, but I had to use some scripts run as root to do so (basically "ifconfig eth0 down", and killing the dhclient before suspend, and "/sbin/dhclient start" when resuming).

I finally got the finger out and started trying to automate this. After a kernel upgrade, upgrading to pcmcia-3.1.14, and hacking the /etc/network/pcmcia script, things seemed to work fairly stably

The hacking to the /etc/pcmcia/network script consists of making 'resume' behave as 'start', and 'suspend' behave like 'stop'. I also copied what the SuSE /sbin/init.d/dhclient script does when starting the demon: give the device an IP number. From the logs it looks like dhclient needs to have an IP number set to be able to get a response from the server. Why this is, I have no idea.

- Steinar

The changes to the network script is given as a diff:

*** /usr/src/pcmcia-cs-3.1.14/etc/network Sat Apr 8 00:18:39 2000 --- /etc/pcmcia/network Tue May 2 18:12:10 2000 

***************
*** 50,56 ****


  case "$ACTION" in

! 'start') 

      test "$IF_PORT" && /sbin/ifport $DEVICE $IF_PORT

--- 50,56 ---- 

  case "$ACTION" in

! 'start'|'resume') 

      test "$IF_PORT" && /sbin/ifport $DEVICE $IF_PORT

***************
*** 94,99 ****
--- 94,102 ----
  		fi
  	    fi
  	elif [ -x /sbin/dhclient ] ; then
+ 	    ifconfig $DEVICE down > /dev/null 2>&1
+ 	    ifconfig $DEVICE 192.168.1.254 broadcast 192.168.1.255 netmask 255.255.255.0 up
+ 	    /sbin/route add -host 255.255.255.255 dev $DEVICE
  	    /sbin/dhclient $DEVICE >/dev/null 2>&1 || exit 1
  	elif [ -x /sbin/pump ] ; then
  	    /sbin/pump $HN -i $DEVICE
***************
*** 142,148 ****
      start_fn $DEVICE
      ;;

! 'stop') 

      stop_fn $DEVICE

--- 145,151 ----
      start_fn $DEVICE
      ;;

! 'stop'|'suspend') 

      stop_fn $DEVICE

***************
*** 226,233 ****
      test "$IPADDR" && /sbin/ifconfig $DEVICE down up
      ;;

- 'suspend'|'resume') - ;; 

  *)
      usage
--- 229,234 ----

Network not resuming after system resumes: Xircom & Dell

Date: 2000, Aug 03
From: Jeff Key jkey

I'm having a problem with the network part of my Xircom multifunction network/modem card restarting after a suspend on a Dell laptop. After booting (or rebooting) the card works fine. But after the system is suspended, the network is not accessible. I can get the card working again with the following commands: 

  /sbin/cardctl suspend
  /sbin/cardctl reset   (resume sometimes (?) works)

Otherwise, the network simply isn't accessible. I tried putting these commands into /etc/sysconfig/apm-scripts/apmcontinue, but that didn't work.

After the system information I'm including lots of other diagnostics (with a few comments here and there) in hopes that somebody can help.

Thanks in advance, Jeff

-----------------------------------------------------------------

Computer: Dell Inspiron 7500

$ uname -a

Linux droplet 2.2.15-4mdk #1 Wed May 10 15:31:30 CEST 2000 i686 unknown

PCMCIA version 3.1.16 

$ /sbin/cardctl ident
Socket 0:
  product info: "Xircom", "CardBus Ethernet 10/100 + Modem 56", "CBEM56G", "1.03"
  manfid: 0x0105, 0x0103
  function: 6 (network)
Socket 1:
  no product info available

$ /sbin/cardctl status
Socket 0:
  3.3V CardBus card
  function 0: [ready]
  function 1: [ready]
Socket 1:
  no card

$ /sbin/cardctl config
Socket 0:
  Vcc 3.3V  Vpp1 3.3V  Vpp2 3.3V
  interface type is "cardbus"
  irq 11 [exclusive] [level]
  function 0:
    io 0x0200-0x0287 [32bit]
  function 1:
    io 0x0200-0x0287 [32bit]
Socket 1:
  not configured

********************** /var/log/messages **********************

#Just before a suspend: 

Jul 31 14:16:35 droplet kernel: usb-uhci.c: interrupt, status 20, frame# 0 
Jul 31 14:16:35 droplet kernel: usb-uhci.c: interrupt, status 28, frame# 0
(lots of these...) 
Jul 31 14:16:35 droplet kernel: usb-uhci.c: interrupt, status 20, frame# 0 
Jul 31 14:16:35 droplet kernel: usb-uhci.c: interrupt, status 28, frame# 0 
Jul 31 14:16:35 droplet cardmgr[422]: executing: './network suspend eth0'
Jul 31 14:16:35 droplet logger: /etc/sysconfig/apm-scripts/suspend called!
Jul 31 14:16:35 droplet cardmgr[422]: executing: './serial suspend ttyS1'
Jul 31 14:16:36 droplet kernel: end_request: I/O error, dev 02:00 (floppy), sector 0 
Jul 31 14:16:36 droplet kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error } 
Jul 31 14:16:36 droplet kernel: hdc: packet command error: error=0x50 
Jul 31 14:16:36 droplet kernel: ATAPI device hdc: 
Jul 31 14:16:36 droplet kernel:   Error: Illegal request -- (Sense key=0x05) 
Jul 31 14:16:36 droplet kernel:   Invalid field in command packet -- (asc=0x24, ascq=0x00) 
Jul 31 14:16:36 droplet kernel:   The failed "Start Stop Unit" packet command was:  
Jul 31 14:16:36 droplet kernel:   "1b 00 00 00 03 00 00 00 00 00 00 00 " 
Jul 31 14:16:36 droplet kernel:   Error in command packet byte 17922 bit 0 
Jul 31 14:16:36 droplet kernel: cdrom: open failed. 
Jul 31 14:16:36 droplet apmd[309]: User Suspend
Jul 31 14:16:56 droplet logger: /etc/sysconfig/apm-scripts/resume called!
Jul 31 14:17:00 droplet apmd[309]: Normal Resume after 00:00:25 (100% 3:20) AC power
Jul 31 14:17:01 droplet cardmgr[422]: executing: './network resume eth0'
Jul 31 14:17:01 droplet cardmgr[422]: executing: './serial resume ttyS1'
Jul 31 14:17:04 droplet kernel:  
Jul 31 14:17:04 droplet kernel: floppy driver state 
Jul 31 14:17:04 droplet kernel: ------------------- 
Jul 31 14:17:04 droplet kernel: now=149125 last interrupt=148629 diff=496 last called handler=c019a778 
Jul 31 14:17:04 droplet kernel: timeout_message=redo fd request 
Jul 31 14:17:04 droplet kernel: last output bytes: 
Jul 31 14:17:04 droplet kernel:  f 80 145907 
Jul 31 14:17:04 droplet kernel:  0 90 145907 
Jul 31 14:17:04 droplet kernel:  1 90 145907 
Jul 31 14:17:04 droplet kernel:  8 81 145907 
Jul 31 14:17:04 droplet kernel: 12 80 148629 
Jul 31 14:17:04 droplet kernel:  0 90 148629 
Jul 31 14:17:04 droplet kernel: 13 90 148629 
Jul 31 14:17:04 droplet kernel:  0 90 148629 
Jul 31 14:17:04 droplet kernel: 1a 90 148629 
Jul 31 14:17:04 droplet kernel:  0 90 148629 
Jul 31 14:17:04 droplet kernel:  3 80 148629 
Jul 31 14:17:04 droplet kernel: c1 90 148629 
Jul 31 14:17:04 droplet kernel: 10 90 148629 
Jul 31 14:17:04 droplet kernel:  7 80 148629 
Jul 31 14:17:04 droplet kernel:  0 90 148629 
Jul 31 14:17:04 droplet kernel:  8 81 148629 
Jul 31 14:17:04 droplet kernel:  f 80 148629 
Jul 31 14:17:04 droplet kernel:  0 90 148629 
Jul 31 14:17:04 droplet kernel:  1 90 148629 
Jul 31 14:17:04 droplet kernel:  8 81 148629 
Jul 31 14:17:04 droplet kernel: last result at 148629 
Jul 31 14:17:04 droplet kernel: last redo_fd_request at 148825 
Jul 31 14:17:04 droplet kernel: 20  1  
Jul 31 14:17:04 droplet kernel: status=0 
Jul 31 14:17:04 droplet kernel: fdc_busy=1 
Jul 31 14:17:04 droplet kernel: DEVICE_INTR=c01a0e54 
Jul 31 14:17:04 droplet kernel: cont=c024aa00 
Jul 31 14:17:04 droplet kernel: CURRENT=c02751cc 
Jul 31 14:17:04 droplet kernel: command_status=-1

# The above floppy stuff repeats a few times... 

Jul 31 14:17:13 droplet kernel:  
Jul 31 14:17:13 droplet kernel: floppy0: floppy timeout called 
Jul 31 14:17:13 droplet kernel: end_request: I/O error, dev 02:00 (floppy), sector 0 
Jul 31 14:17:13 droplet kernel: FAT bread failed 
Jul 31 14:17:13 droplet kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error } 
Jul 31 14:17:13 droplet kernel: hdc: packet command error: error=0x50 
Jul 31 14:17:13 droplet kernel: ATAPI device hdc: 
Jul 31 14:17:13 droplet kernel:   Error: Illegal request -- (Sense key=0x05) 
Jul 31 14:17:13 droplet kernel:   Invalid field in command packet -- (asc=0x24, ascq=0x00) 
Jul 31 14:17:13 droplet kernel:   The failed "Start Stop Unit" packet command was:  
Jul 31 14:17:13 droplet kernel:   "1b 00 00 00 03 00 00 00 00 00 00 00 " 
Jul 31 14:17:13 droplet kernel:   Error in command packet byte 7368 bit 0 
Jul 31 14:17:13 droplet kernel: cdrom: open failed. 


#------------------------------------------------------------------------
# The network is not accessible at this point (after resuming the system).
# Here are some more /var/log/messages AFTER "cardctl suspend" and 
# "cardctl reset":
#------------------------------------------------------------------------


Jul 31 14:18:40 droplet cardmgr[422]: executing: './network suspend eth0'
Jul 31 14:18:40 droplet cardmgr[422]: executing: './serial suspend ttyS1'
Jul 31 14:18:40 droplet kernel: tty01 unloaded 
Jul 31 14:18:40 droplet kernel: cs: cb_free(bus 32) 
Jul 31 14:18:40 droplet kernel: floppy0: unexpected interrupt  
Jul 31 14:18:40 droplet kernel: floppy0: sensei repl[0]=c0 repl[1]=0  
Jul 31 14:18:40 droplet kernel: floppy0: sensei repl[0]=c1 repl[1]=0  
Jul 31 14:18:40 droplet kernel: floppy0: sensei repl[0]=c2 repl[1]=0  
Jul 31 14:18:40 droplet kernel: floppy0: sensei repl[0]=c3 repl[1]=0  
Jul 31 14:18:40 droplet kernel: end_request: I/O error, dev 02:00 (floppy), sector 0 
Jul 31 14:18:40 droplet kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error } 
Jul 31 14:18:40 droplet kernel: hdc: packet command error: error=0x50 
Jul 31 14:18:40 droplet kernel: ATAPI device hdc: 
Jul 31 14:18:40 droplet kernel:   Error: Illegal request -- (Sense key=0x05) 
Jul 31 14:18:40 droplet kernel:   Invalid field in command packet -- (asc=0x24, ascq=0x00) 
Jul 31 14:18:40 droplet kernel:   The failed "Start Stop Unit" packet command was:  
Jul 31 14:18:40 droplet kernel:   "1b 00 00 00 03 00 00 00 00 00 00 00 " 
Jul 31 14:18:40 droplet kernel:   Error in command packet byte 17922 bit 0 
Jul 31 14:18:40 droplet kernel: cdrom: open failed. 
Jul 31 14:18:40 droplet cardmgr[422]: shutting down socket 0
Jul 31 14:18:40 droplet cardmgr[422]: executing: './network stop eth0'
Jul 31 14:18:40 droplet cardmgr[422]: executing: './serial stop ttyS1'
Jul 31 14:18:41 droplet kernel: end_request: I/O error, dev 02:00 (floppy), sector 0 
Jul 31 14:18:41 droplet kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error } 
Jul 31 14:18:41 droplet kernel: hdc: packet command error: error=0x50 
Jul 31 14:18:41 droplet kernel: ATAPI device hdc: 
Jul 31 14:18:41 droplet kernel:   Error: Illegal request -- (Sense key=0x05) 
Jul 31 14:18:41 droplet kernel:   Invalid field in command packet -- (asc=0x24, ascq=0x00) 
Jul 31 14:18:41 droplet kernel:   The failed "Start Stop Unit" packet command was:  
Jul 31 14:18:41 droplet kernel:   "1b 00 00 00 03 00 00 00 00 00 00 00 " 
Jul 31 14:18:41 droplet kernel:   Error in command packet byte 17922 bit 0 
Jul 31 14:18:41 droplet kernel: cdrom: open failed. 
Jul 31 14:18:41 droplet cardmgr[422]: executing: 'modprobe -r tulip_cb'
Jul 31 14:18:41 droplet cardmgr[422]: executing: 'modprobe -r serial_cb'
Jul 31 14:18:41 droplet cardmgr[422]: executing: 'modprobe -r cb_enabler'
Jul 31 14:18:41 droplet kernel: cs: cb_alloc(bus 32): vendor 0x115d, device 0x0003 
Jul 31 14:18:41 droplet cardmgr[422]: initializing socket 0
Jul 31 14:18:41 droplet cardmgr[422]: socket 0: Xircom CBEM56G-100 CardBus 10/100 Ethernet + 56K Modem
Jul 31 14:18:41 droplet cardmgr[422]: executing: 'modprobe cb_enabler'
Jul 31 14:18:41 droplet cardmgr[422]: executing: 'modprobe tulip_cb'
Jul 31 14:18:41 droplet cardmgr[422]: executing: 'modprobe serial_cb'
Jul 31 14:18:41 droplet cardmgr[422]: + /lib/modules/2.2.15-4mdk/pcmcia/serial_cb.o: invalid parameter parm_irq
Jul 31 14:18:41 droplet cardmgr[422]: + /lib/modules/2.2.15-4mdk/pcmcia/serial_cb.o: insmod /lib/modules/2.2.15-4mdk/pcmcia/serial_cb.o failed
Jul 31 14:18:41 droplet cardmgr[422]: + /lib/modules/2.2.15-4mdk/pcmcia/serial_cb.o: insmod serial_cb failed
Jul 31 14:18:41 droplet cardmgr[422]: modprobe exited with status 255
Jul 31 14:18:41 droplet cardmgr[422]: executing: 'insmod /lib/modules/2.2.15-4mdk/pcmcia/serial_cb.o'
Jul 31 14:18:41 droplet kernel: cs: cb_config(bus 32) 
Jul 31 14:18:41 droplet kernel:   fn 0 bar 2: mem 0x60013000-0x600137ff 
Jul 31 14:18:41 droplet kernel:   fn 0 bar 3: mem 0x60012000-0x600127ff 
Jul 31 14:18:41 droplet kernel:   fn 1 bar 1: io 0x280-0x287 
Jul 31 14:18:41 droplet kernel:   fn 1 bar 2: mem 0x60011000-0x600117ff 
Jul 31 14:18:41 droplet kernel:   fn 1 bar 3: mem 0x60010000-0x600107ff 
Jul 31 14:18:41 droplet kernel:   fn 0 bar 1: io 0x200-0x27f 
Jul 31 14:18:41 droplet kernel:   fn 0 rom: mem 0x6000c000-0x6000ffff 
Jul 31 14:18:41 droplet kernel:   fn 1 rom: mem 0x60008000-0x6000bfff 
Jul 31 14:18:41 droplet kernel:   irq 11 
Jul 31 14:18:41 droplet kernel: tulip_attach(device 20:00.0) 
Jul 31 14:18:41 droplet kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford) 
Jul 31 14:18:41 droplet kernel: eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x200, 00:10:A4:C1:CF:39, IRQ 11. 
Jul 31 14:18:41 droplet kernel: eth0:  MII transceiver #0 config 3100 status 7809 advertising 01e1. 
Jul 31 14:18:41 droplet kernel: serial_attach(device 20:00.1) 
Jul 31 14:18:41 droplet kernel: tty01 at 0x0280 (irq = 11) is a 16550A 
Jul 31 14:18:41 droplet cardmgr[422]: executing: './network start eth0'
Jul 31 14:18:41 droplet cardmgr[422]: executing: './serial start ttyS1'

# Now everything works

********************** /proc/buc/pccard/00 **********************

Before suspend, cat /proc/bus/pccard/00/*:

00000000 00000006 30000868 00000000 00000033 00000000 00000000 00000000 84 6e 19 10 00 08 00 00 00 00 01 00 00 00 01 00 00 00 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 type: TI 1225 psock: 0 bus: 00 devfn: 04.0 cardbus: 20 ac1c104c 02100007 06070001 0082a808 68000000 220000a0 20222000 60008000 60013000 00000000 00000000 00000200 00000284 00000000 00000000 0700010b 009e1028 00000001 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 2044b060 00000000 00000000 01021c72 606683c0 00000000 00000000 00000000 7e210001 00808000 00000801 0000001f 00000000 00000000 00000000 00000000

After suspend, cat /proc/bus/pccard/00/*:

00000000 00000006 30000868 00000000 00000033 00000000 00000000 00000000 84 6e 19 10 00 08 00 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00 c0 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 type: TI 1225 psock: 0 bus: 00 devfn: 04.0 cardbus: 20 ac1c104c 02100007 06070001 0082a808 68000000 220000a0 20222000 60008000 60013000 00000000 00000000 00000200 00000284 00000000 00000000 0700010b 009e1028 00000001 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 2044b060 00000000 00000000 01021c72 606683c0 00000000 00000000 00000000 7e210001 00808000 00000819 0000001f 00000000 00000000 00000000 00000000

1. It is a known bug by David Hinds, 2000, Aug 03
(_ Thanks, but...no hope? by Jeff Key, 2000, Aug 03
(_ There is always hope by David Hinds, 2000, Aug 03

Warning: Suspend crashes if X is running

Date: 2000, Aug 04
From: David Brooks dbrooks

This is an odd and annoying little problem! With a NetGear FA510C network card suspend works fine from the console if you 'cardctl eject' the card first, and is properly detected when the system is resumed.

However, if XFree86_SVGA [neomagic NM2093 chipset] is running, then any attempt to suspend the system instead results in either a freeze or an immediate powerdown [as if I had turned the power off manually without running 'shutdown'].

This also happens if I switch back to a virtual console first. I found that the following commands run from the console seemed to provide a solution:

ifdown eth0; cardctl eject 0; killall -STOP X; apm -s; killall -CONT X

...and was quite happy, until I realized that for some unknown reason this only works intermitantly, other times it freezes or reboots the system as before. This only happens if X windows is being used. Weird, [and annoying]!

--David Brooks

PCMCIA Power Management and APM

[ Add Message ]  to: "PCMCIA Power Management and APM"

[ Members ]  [ Subscribe ]  [ Admin Mode ] 
[ Show Frames ]  [ Help for HyperNews at pcmcia-cs.sourceforge.net 1.10 ]