Attached are a dmesg log from my laptop resuming after a software suspend with a stock 2.6.2 kernel, and the config that 2.6.2 kernel was compiled with. Usually after resume the network is back and happy, but this time it went "boing". Specifically: [root@driftwood root]# ifconfig eth0 up SIOCSIFFLAGS: Device or resource busy [root@driftwood root]# The relevant section of the dmesg output seems to be: hda: Wakeup request inited, waiting for !BSY... hda: start_power_step(step: 1000) blk: queue cb535000, I/O limit 4095Mb (mask 0xffffffff) hda: completing PM request, resume hdc: Wakeup request inited, waiting for !BSY... hdc: start_power_step(step: 1000) hdc: completing PM request, resume eth0: New link status: Connected (0001) Restarting tasks... done request_module: failed /sbin/modprobe -- char-major-10-135. error = 256 eth0: New link status: Connected (0001) eth0: New link status: Connected (0001) hermes @ IO 0x100: Timeout waiting for command completion. eth0: Error -110 disabling MAC port hermes @ IO 0x100: Timeout waiting for command completion. eth0: Error -110 enabling MAC port Any clues? Rob P.S. No, I can't pop the card and put it back in, it's built into the machine. This laptop has two cardbus busses, one for external cards and one for the built in wireless, and cardctl gets a touch confused at times when there are two cardbus busses in one machine. I just sent a "cardctl reset 0", which seems to have gotten the driver to talk to the card again, but dhclient isn't getting any response from the hub... Power cycle time. Oh well, I've been meaning to upgrade to 2.6.3 anyway... :)