2.6.35 hangs on early boot in KVM
in [Kernel]
|
Prev: [ANNOUNCE] 2.6.33.7-rt29
Next: [PATCH 1/2 block#for-2.6.36] bio, fs: update RWA_MASK, READA and SWRITE to match the corresponding BIO_RW_* bits
From: Tvrtko Ursulin on 3 Aug 2010 11:20 On Tuesday 03 Aug 2010 15:57:03 Tvrtko Ursulin wrote: > On Tuesday 03 Aug 2010 15:51:08 Avi Kivity wrote: > > On 08/03/2010 12:28 PM, Tvrtko Ursulin wrote: > > > I have basically built 2.6.35 with make oldconfig from a working > > > 2.6.34. Latter works fine in kvm while 2.6.35 hangs very early. I see > > > nothing after grub (have early printk and verbose bootup enabled), > > > just a blinking VGA cursor and CPU at 100%. > > > > Please copy kvm(a)vger.kernel.org on kvm issues. > > > > > CONFIG_PRINTK_TIME=y > > > > Try disabling this as a workaround. > > I am in the middle of a bisect run with five builds left to go, currently I > have: > > bad 537b60d17894b7c19a6060feae40299d7109d6e7 > good 93c9d7f60c0cb7715890b1f9e159da6f4d1f5a65 Bisect is looking good, narrowed it to ten revisions, but I am not sure to make it to the end today: bad cb41838bbc4403f7270a94b93a9a0d9fc9c2e7ea good 41d59102e146a4423a490b8eca68a5860af4fe1c One interesting waning spotted: include/config/auto.conf:555:warning: symbol value '-fcall-saved-ecx -fcall- saved-edx' invalid for ARCH_HWEIGHT_CFLAGS Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom. Company Reg No 2096520. VAT Reg No GB 348 3873 20. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Tvrtko Ursulin on 3 Aug 2010 11:40 On Tuesday 03 Aug 2010 16:17:20 Tvrtko Ursulin wrote: > On Tuesday 03 Aug 2010 15:57:03 Tvrtko Ursulin wrote: > > On Tuesday 03 Aug 2010 15:51:08 Avi Kivity wrote: > > > On 08/03/2010 12:28 PM, Tvrtko Ursulin wrote: > > > > I have basically built 2.6.35 with make oldconfig from a working > > > > 2.6.34. Latter works fine in kvm while 2.6.35 hangs very early. I see > > > > nothing after grub (have early printk and verbose bootup enabled), > > > > just a blinking VGA cursor and CPU at 100%. > > > > > > Please copy kvm(a)vger.kernel.org on kvm issues. > > > > > > > CONFIG_PRINTK_TIME=y > > > > > > Try disabling this as a workaround. > > > > I am in the middle of a bisect run with five builds left to go, currently > > I have: > > > > bad 537b60d17894b7c19a6060feae40299d7109d6e7 > > good 93c9d7f60c0cb7715890b1f9e159da6f4d1f5a65 > > Bisect is looking good, narrowed it to ten revisions, but I am not sure to > make it to the end today: > > bad cb41838bbc4403f7270a94b93a9a0d9fc9c2e7ea > good 41d59102e146a4423a490b8eca68a5860af4fe1c > > One interesting waning spotted: > > include/config/auto.conf:555:warning: symbol value '-fcall-saved-ecx > -fcall- saved-edx' invalid for ARCH_HWEIGHT_CFLAGS Copying Peter and Borislav, guys please look at the above warning. I am bisecting a non-bootable 2.6.35 under KVM and while I am not there yet, it is close to the hweight commit (cb41838bbc4403f7270a94b93a9a0d9fc9c2e7ea) and I spotted this warning. Tvrtko Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom. Company Reg No 2096520. VAT Reg No GB 348 3873 20. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Borislav Petkov on 3 Aug 2010 11:50 From: Tvrtko Ursulin <tvrtko.ursulin(a)sophos.com> Date: Tue, Aug 03, 2010 at 11:31:02AM -0400 > > One interesting waning spotted: > > > > include/config/auto.conf:555:warning: symbol value '-fcall-saved-ecx > > -fcall- saved-edx' invalid for ARCH_HWEIGHT_CFLAGS > > Copying Peter and Borislav, guys please look at the above warning. I am > bisecting a non-bootable 2.6.35 under KVM and while I am not there yet, it is > close to the hweight commit (cb41838bbc4403f7270a94b93a9a0d9fc9c2e7ea) and I > spotted this warning. That's because you're at a bisection point before the hweight patch but your .config already contains the ARCH_HWEIGHT_CFLAGS variable because of the previous bisection point which contained the hweight patch. I think this can be safely ignored. -- Regards/Gruss, Boris. Advanced Micro Devices GmbH Einsteinring 24, 85609 Dornach General Managers: Alberto Bozzo, Andrew Bowd Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen Registergericht Muenchen, HRB Nr. 43632 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Tvrtko Ursulin on 3 Aug 2010 12:10 On Tuesday 03 Aug 2010 16:49:01 Borislav Petkov wrote: > From: Tvrtko Ursulin <tvrtko.ursulin(a)sophos.com> > Date: Tue, Aug 03, 2010 at 11:31:02AM -0400 > > > > One interesting waning spotted: > > > > > > include/config/auto.conf:555:warning: symbol value '-fcall-saved-ecx > > > -fcall- saved-edx' invalid for ARCH_HWEIGHT_CFLAGS > > > > Copying Peter and Borislav, guys please look at the above warning. I am > > bisecting a non-bootable 2.6.35 under KVM and while I am not there yet, > > it is close to the hweight commit > > (cb41838bbc4403f7270a94b93a9a0d9fc9c2e7ea) and I spotted this warning. > > That's because you're at a bisection point before the hweight patch but > your .config already contains the ARCH_HWEIGHT_CFLAGS variable because > of the previous bisection point which contained the hweight patch. > > I think this can be safely ignored. Yep, bisect pointed to another commit so I continued another part of this thread. Thanks for the explanation! Tvrtko Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom. Company Reg No 2096520. VAT Reg No GB 348 3873 20. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Eric W. Biederman on 3 Aug 2010 16:40
Tvrtko Ursulin <tvrtko.ursulin(a)sophos.com> writes: > On Tuesday 03 Aug 2010 16:17:20 Tvrtko Ursulin wrote: >> On Tuesday 03 Aug 2010 15:57:03 Tvrtko Ursulin wrote: >> > On Tuesday 03 Aug 2010 15:51:08 Avi Kivity wrote: >> > > On 08/03/2010 12:28 PM, Tvrtko Ursulin wrote: >> > > > I have basically built 2.6.35 with make oldconfig from a working >> > > > 2.6.34. Latter works fine in kvm while 2.6.35 hangs very early. I see >> > > > nothing after grub (have early printk and verbose bootup enabled), >> > > > just a blinking VGA cursor and CPU at 100%. >> > > >> > > Please copy kvm(a)vger.kernel.org on kvm issues. >> > > >> > > > CONFIG_PRINTK_TIME=y >> > > >> > > Try disabling this as a workaround. >> > >> > I am in the middle of a bisect run with five builds left to go, currently >> > I have: >> > >> > bad 537b60d17894b7c19a6060feae40299d7109d6e7 >> > good 93c9d7f60c0cb7715890b1f9e159da6f4d1f5a65 >> >> Bisect is looking good, narrowed it to ten revisions, but I am not sure to >> make it to the end today: >> >> bad cb41838bbc4403f7270a94b93a9a0d9fc9c2e7ea >> good 41d59102e146a4423a490b8eca68a5860af4fe1c > > Bisect points the finger to "x86, ioapic: In mpparse use mp_register_ioapic" > (cf7500c0ea133d66f8449d86392d83f840102632), so I am copying Eric. No idea > whether this commit is solely to blame or it is a combined interaction with > KVM, but I am sure you guys will know. > > If you want me to test something else please shout. Interesting. This is the second report I have heard of no VGA output and a hang early in boot, that was bisected to this commit. Since I could not reproduce it I was hoping it was a fluke with a single piece of hardware, but it appears not. There was in fact an off by one bug in that commit, but if that had been the issue 2.6.35 would have booted ok. There was nothing in that commit that should have prevented early output, and in fact I can boot with a very similar configuration. So I am trying to figure out what pieces are interacting to cause this failure mode to happen. What version of kvm are you running on your host (in case that matters)? I want to reproduce this myself so I can start guessing what weird interactions are going on. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |