* Tobias Jakobi <tjakobi@xxxxxxxxxxxxxxxxxxxxx> [140519 14:19]: > Daniel Lezcano wrote: > > > > So apparently Santosh, Kevin and Alex say they are not facing the > > issue anymore with the revert. But Tobias is still facing this issue. > > > > There is this simple program [1] which usually makes cpuidle to hang > > the system more quickly when there is a problem somewhere. May be > > worth to check with it. > > > > Hope that helps. > > > > -- Daniel > > > > [1] > > https://git.linaro.org/power/pm-qa.git/blob/HEAD:/cpuidle/cpuidle_killer.c > > > Hello, > > just to clarify. I never encountered the boot failure problem on my > Panda ES in the first place. The issue with CPU_IDLE for me, like I also > say in the bugreport, showed itself through instability of the USB. I > saw the boot issue on the ml, read that it was caused by CPU_IDLE, and > thought I should make Tony aware that I have a similar problem. > > Now, after applying the latest version of the patch that Santosh > proposed, the situation with CPU_IDLE improves. But it is still not > stable for me, since after some while, working with an SSH session of > WiFi (which IIRC is not connected via USB on the board), this 'BUG' > storm hits. This does _not_ happen when I disable CPU_IDLE completly. OK that seems like a different problem. > But even if I don't connect via WiFi at all, just boot and let me system > run with serial console connected, after some time I get a kernel 'WARNING': > http://www.math.uni-bielefeld.de/~tjakobi/archive/dmesg.1.log > > So something with CPU_IDLE is not right here. However I can't say if > it's exactly this boot issue which this thread was initially about. > Maybe seperate issues are at work here, who knows. > > Anyway, I'm going to have a look at that cpuidle killer thingy later. OK. I gave it a try, but did not get any errors at least after about 30 minutes of testing on my panda es. I'll apply the patch from Santosh as that gets things booting again with linux next. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
