Few more things: There was no flashing capslock during the test sequence - but at the next reboot the system did detect the crash, hence bug #356307.
Re the DebuggingKernelSuspendHibernateResume Qs: Is this really a failure? I would think so, yes. I should be able to close the lid and have the system suspend cleanly (providing there are no hardware or driver bugs). Is this a repetition of a previous failure? No AFAIK; I'm treating this report as the master report for this failure. Did the machine break while going to sleep or waking up? While suspending - it never made to a suspended state. Is it reproducible? At will. Refer to comment #5 and bug #356307 Did it work before? No. I've only had this machine a short while and have not tried this with another machine. Suspend was to-RAM, not to-disk, so the hibernate Qs don't apply. As a side note, when I was attempting to get the withZydas lspci and lsusb output, I had for the first time a kernel panic as soon as I plugged the Zydas in - but I am unable to reproduce and can find no relevant information in the log files. -- [Dell Inc. Studio 1535] suspend/resume failure https://bugs.launchpad.net/bugs/349985 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
