On Wed, Feb 25, 2009 at 9:18 PM, Rogan Creswick > Ah.. that did help narrow things down a bit! I can reproduce the > problem at home by: > > * removing the tablet from the ultrabase > * putting it to sleep (closing the lid, and waiting a few min.) > * unplugging the power from my WAP > * wake the laptop up (while not in the ultrabase) > > This *only* happens on the first suspend/resume from the dock, and > only if the wap goes away while the tablet is asleep. > >>> Is it possible that the ultrabase (driver) is involved? >> >> Could be -- I'll see if I can learn more when I get home tonight. > > It seems like it must be involved somehow. It's been a long day, so > I'm still absorbing implications of all this - I'll try to pursue some > more options tomorrow (rmmoding the wifi drivers/ultrabase driver on > sleep and insmoding them on resume, anyway.)
I have a bit more info, but not a lot in the way of solutions. I can successfully resume the tablet if I plug it into a dock *before* waking it up -- it seems that it must be resuming w/out either of the dock or the wifi inorder to hit the problem case. The next logical thing seemed to be to rmmod the dock module before putting the tablet to sleep, but I've been unable to do that, and I don't know why. The dock module is called "dock", and it depends on libata, libata depends on ata_generic, pata_acpi, ata_piix, and ahci. I can't rmmod the dock module w/out rmmoding all the others, and for the most part that goes well. However, I've been unable to rmmod ahci. $ sudo rmmod ahci ERROR: Module ahci is in use $ lsmod | grep ahci 86: ahci 37132 2 87: libata 177312 1 ahci How can I find out what is using ahci? (This is all happening when the system is *out* of the dock, so I'd assume it's not *really* using ahci...) I have a feeling it's hald, but I think I want hald running ;) --Rogan _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
