On Sun, 22 Jun 2014, Toralf Förster wrote: > On 06/20/2014 10:53 PM, Alan Stern wrote: > > You mean 3.15 plus the patch I sent? > > > >> > tfoerste@n22 ~/tmp $ sudo su - > >> > n22 ~ # cat /sys/kernel/debug/usb/usbmon/2u >/tmp/right > >> > ^C > >> > > >> > n22 ~ # cat /sys/kernel/debug/usb/usbmon/2u >/tmp/wrong > >> > ^C > >> > > >> > For the second command : Before I s2ram'ed the system I switched the USB > >> > hub (where the keyboardm, the mouse and a printer was attached) from the > >> > "right" port to the "wrong" port. > > Is this the same as what you get from plain 3.15 with no patches? > > > > Sorry I've been too busy with other things to look at this yet. I'll > > try to get to it next week. > > Ok, I repeated those steps with current kernel 3.15.1 > > First without your patch, after that with your patch - all 4 traces are > attached.
Sorry I haven't gotten back to this... I was busy with other things and lost track of it. Toralf, I looked through your usbmon traces. Their message is clear: This isn't a software problem. According to the usbmon traces, the patch had no significant effect. The reason things worked better with the "right" port than the "wrong" port is very simple. When the hub (with the attached mouse, printer, and keyboard) was plugged into the "wrong" port, it got disconnected electronically during the suspend! It couldn't send any wakeup messages. This seems like a hardware problem in the port itself, or in one of the chips on the motherboard. No software change will fix it; all you can do is avoid using that port for devices that should wake up the system. Adam, your problem seems to be completely different. Your system wakes up okay from suspend, but not from hibernation. Was there ever any kernel version where USB wakeup from hibernation did work? 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
