Thought this ought be in our mailing list archives. Might be useful someday.
[EMAIL PROTECTED]: > I have a Inspiron 7500 and I avoid closing the lid because of this. > Care to share the secrets? lessee... I diagnosed suspend problems by pressing the cover-down button for a few seconds while at a text console. pressing the button triggers a suspend, and releasing it gives me back the screen so I can see what's going on. for some reason, I don't get the screen back in X. main diagnostic tools were looking in /var/log/messages, using 'ps' and 'strace' to see what was hung, and adding diagnostic 'logger' statements in various scripts. the problems I had were - one of the network cards I was using wouldn't resume after a suspend, which I discovered by just trying 'cardctl suspend' and 'cardctl resume'. I coped with that by forcing the apmd script to use eject/insert instead. - the suspend scripts tried to access NFS filesystems after the network card was suspended. symptom is: if I manually eject the network card and insert it again, the laptop finishes suspending. there were two causes of this: - pcmcia scripts want to use 'fuser' for various reasons. in Red Hat 7, you can say 'NO_FUSER=yes' in /etc/sysconfig/pcmcia. in Red Hat 6.2, I coped by defining a null fuser function in one of the pcmcia scripts, I forget which. fuser () { false; } - in Red Hat 7, /etc/sysconfig/apm-scripts/apmscript wants to use 'pidof', which goes and stats every /proc/*/exe file, which will hang on NFS if any running program is on an NFS filesystem. coped with that by adding a null pidof function to the end of /etc/sysconfig/apmd pidof () { false; } urrr... there may have been another problem in Red Hat 6.2; I didn't keep a copy of all my 6.2 config. --
