On Thu, Jun 26, 2014 at 07:59:19AM -0700, Kevin Hilman wrote: > I agree that the u-boot bug needs to be fixed, and FWIW, I updated my > u-boot and haven't seen the boot failure yet after several boots with > next-20140625. > > That being said, since it's not always feasible/practical to update > u-boot, and when it comes down to it, this is still a kernel > regression, we should also fix the kernel to sanity check the values > coming from u-boot, like it was doing before. It wasn't sanity checking the values (there is some sanity checking, but the sanity checking doesn't catch this). What caught it was that the kernel was configured to only look at the first 8 of the 12 meminfo entries with ATAGs. Since we no longer have that limit, all meminfo entries are now looked at (since the kernel doesn't need the limit.) We could add back a soft-limit on the number of meminfo entries, but this has to be platform specific. Another entry to go into the mach_info structures? -- FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly improving, and getting towards what was expected from it. -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |