On Mon, 28 Nov 2016 21:57:11 +0900, OGAWA Hirofumi <hirofumi@xxxxxxxxxxxxxxxxxx> wrote: > OGAWA Hirofumi <hirofumi@xxxxxxxxxxxxxxxxxx> writes: > Hm, this issue might be same with 4efca4ed05cbdfd13ec3e8cb623fb77d6e4ab187. > But it was already including into 4.9-rc7. My bad, it was rc6, not rc9. > can you try 4.9-rc7 if older one? Updated & rebased, building. > I couldn't reproduce that "no CRC" > issue with debian kernel's .config I did not diff recently my .config with debian's. I think I based it on Debian's 4.2 and then let it evolve "naturally" following vanilla. I checked all diffs against Debian's 4.8 and reduced it a lot (mostly new drivers which I did not enable). Doing so, I discovered that I somehow did not have "CONFIG_MODVERSIONS" set at all (not even the "is not set" comment). 4.9-rc7 is done building, there is no warning about CRC anymore - I'm not sure whether this comes from rc7 or MODVERSIONS. I can check if you think it is valuable. Resulting kernel booted successfully once, but I must do several more tries before being able to tell if it reliably does so. I also want to check rc7 without your patches, to compare boot failure rate. For reference, the I pushed the source I built in https://github.com/vpelletier/linux/tree/ts651_4.9-rc7 Please do check I did not do mistakes when resolving conflicts (the 2 last commits). Regards, -- Vincent Pelletier -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
