> > It's getting more strange. I ran 4.4-rc8-00005 for 2-3 weeks nonstop, > > doing git clone and make -j4 in a loop, on both V240 and V440. Worked > > 100% stable. > > > > Then I git git pull from kernel.org, tried to compile 4.5-rc1 (or was it > > rc2 already), on the same running 4.4.0-rc8-00005 and it rebooted, on > > both V240 and V440. > > sorry for not getting back sooner - was on the road, and will be > mostly offline again next week. But the symptoms sound like there > might be a memory and/or compiler issue. I'm not sure how to check this > theory out.. maybe someone else with more expertise in this space > can check? Hmm, probability-wise that is not very likely that at least 4 different machines (V240, V440, E450, V100) grow a hardware error at 4.3 timeframe and start rebooting spontaneously? Maybe something with our memory detection / bootmeme / memory ranges has changed? Il will try more to find a way to reproduce the problem. Maybe putting aside an old git tree state (how do I get one?), then at each boot copy it and pull it and then compile. -- Meelis Roos (mroos@xxxxxxxx) -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
