> Alas there are no messages from the firewire drivers in this log. Not even > a message from PCI core that a firewire-ohci driver method failed. Hence > we (linux1394-devel people) have nothing to go on yet. This is because I can't get the message buffer from the hung kernel. The log is from a forcefully rebooted kernel which logs the trace information which is stored in the RTC between reboots (supposedly this is the only non-volatile register available). You can see that overwriting the RTC results in date in the 2020's. More here: https://wiki.ubuntu.com/DebuggingKernelSuspend#%22resume-trace%22%20debugging%20procedure%20for%20finding%20buggy%20drivers > The downstream tracker item is: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/732641 > > It contains a somewhat different failure description from a 2.6.35 Ubuntu > kernel: > ... > > JaÅa, are all of the dmesg messages in this report from the same session? dmesg messages on Launchpad are from 2.6.35 as it is the shipped kernel in Ubuntu 10.10. In the comment on Launchpad you can also see dmesg from 2.6.38-rc8 that was latest mainline at the time. On this kernel bugzilla I posted the dmesg of the just released 2.6.38 stable kernel because I think this version is most relevant at this time (right?). > Linux-pm folks, why is the PM Restore failure reported at 0.714873 but the > system proceeds and logs successful attachment of firewire-ohci's pci_probe > to the PCI device? I think you can find an explanation for this in my first paragraph of this email. > Can somebody comment on the phenomenon that VT switching was affected? ... > Well, maybe firewire-core hung in a workqueue job which in turn prevented > subsequent processing of other subsystems' workqueue jobs. This can be > much more of a problem with a kernel like 2.6.35 than with newer ones > with concurrency managed workqueues (2.6.36 and later). The VT switching is only possible on 2.6.35 for me. That is why I only mentioned it on Launchpad. With .38 my display receives no signal after attempting a resume. > (JaÅa, prefer reply-to-all for responses. Thanks for your reports so far.) * Stefan, sorry for duplicate, replying to rest of your CC * Thanks for your patience, this is my first bug report here. :) _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
