-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | Andy Green wrote: |> Somebody in the thread at some point said: |> | And, well, the kernel I've compiled from the stable-tracking branch |> | doesn't resume at all from suspending :(. Is this a known issue? |> |> Not known yet, anyway... do you have a debug board? If so |> stable-tracking still has a debug feature in that pressing AUX key |> during "suspend" will try to OOPS the kernel, and another patch causes |> dumping of pending syslog stuff in case of panic or OOPS. |> |> The end result is you can "usually" get detailed information on a hung |> suspend or resume... if you have a debug board. | | No, I haven't it... Btw I can report that the latest images you built | and linked here was resuming well. Latest git seems to have some | issues... :(
Well the last few days I have evolved a new way to merge rebases, andy-tracking should have a workable commit history back to the patches on there starting "MERGE", "6 days ago" according to gitweb. So if you think it was OK six days ago it should now be possible to peel back the top 16 patches anyway in the normal git way until it works again and identify what broke it. The obvious guess is WLAN related stuff but only because it was around suspend / resume. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkupTkACgkQOjLpvpq7dMpSyACdE5EREiw7r4PGj5pZ/mRhX2WJ x78An1lqS01WxBs/RGMLVJoJsBR2hgg1 =U/b+ -----END PGP SIGNATURE-----
