On Sat, Jun 01, 2013 at 05:37:05PM +0200, Jens Taprogge wrote: > On Fri, May 31, 2013 at 05:16:49PM -0700, John Stultz wrote: > > On 05/31/2013 04:42 PM, Jens Taprogge wrote: > > >On Fri, May 31, 2013 at 02:14:47PM -0700, John Stultz wrote: > > >>On 05/31/2013 05:06 AM, Jens Taprogge wrote: > > >>>So, in the case of the reverted v3.9.4 with CONFIG_CPU_FREQ_STAT=y, > > >>>CONFIG_X86_VERBOSE_BOOTUP makes a difference. To update the little > > >>>table from above: > > >>> > > >>>With d96ac6f2 reverted: > > >>> > > >>> CONFIG_CPU_FREQ_STAT=n works > > >>> CONFIG_CPU_FREQ_STAT=y and CONFIG_X86_VERBOSE_BOOTUP=y does not work > > >>> CONFIG_CPU_FREQ_STAT=y and CONFIG_X86_VERBOSE_BOOTUP=n works > > >>Ok. None of this is yet making any sense to me. (And I worry > > >>enumerating all the mix and match of configs that work or don't only > > >>blurs the issues). > > >> > > >>Few base questions: > > >>1) What distro is this on? > > >arch linux > > > > > >>2) What gcc version are you using? > > >gcc (GCC) 4.8.0 20130502 (prerelease) > > > > (Sorry, I'm not very familiar with arch) Are you able to also > > install a 4.7 gcc in parallel to try to build with? > > > > If so, you might want to try that. Your results are just weird > > enough I want to just be sure we're not chasing compiler caused > > ghosts. > > I will compile gcc4.6 and see if using that makes any difference. I have compiled two of the broken configurations with gcc-4.6 and both boot up. I am not sure how to proceed from here. Best Regards Jens -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html