On Tue, 18 Mar 2014, Peter Münster wrote: > Hi, > > Commit 0aa2832dd0d9d8609fd8f15139bc7572541a1215 introduces a problem for > my system:
You should include the name of the commit along with the hash ID; otherwise nobody will know what it is unless they go to the trouble of looking it up for themselves. You also should address your email to the author of the commit. Otherwise your message is very likely to get overlooked. > When it wakes up after s2ram, it freezes. Screen is black, keyboard > does not work, no ssh-connection. Just the network-ping works. What do you get if you boot with no_console_suspend on the kernel command line and do "echo 8 >/proc/sys/kernel/printk" before starting the suspend? Also, can you turn on CONFIG_USB_DEBUG? > Please see here for more details, especially information about the > hardware: https://bugzilla.novell.com/show_bug.cgi?id=868315 What happens if you run a kernel that doesn't have that commit, such as 3.9 or earlier, and you turn off CONFIG_USB_SUSPEND? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
