From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Failure to boot default Debian wheezy (pvops) kernel on 4.2-rc2 Date: Fri, 17 Aug 2012 14:18:19 +0100 Message-ID: <502E449B.2030502@eu.citrix.com> References: <20120817130757.GD31903@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20120817130757.GD31903@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: Stefano Stabellini , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 17/08/12 14:07, Konrad Rzeszutek Wilk wrote: > On Fri, Aug 17, 2012 at 12:17:15PM +0100, George Dunlap wrote: >> I just tried to install Xen-4.2.0-rc2 on a Debian wheezy system, but >> couldn't boot under Xen 4.2. The box is an 8-core AMD, I think >> Barcelona. The wheezy kernel is 3.2.21-3, 32-bit version. >> >> The problems seem to have started here: >> >> -- snip -- >> [ 0.060280] ACPI: Core revision 20110623^M^M >> [ 0.072384] Performance Events: Broken BIOS detected, complain to >> your hardware vendor.^M^M >> [ 0.076014] [Firmware Bug]: the BIOS has corrupted hw-PMU resources >> (MSR c0010000 is 530076)^M^M >> [ 0.080007] AMD PMU driver.^M^M >> [ 0.082864] ------------[ cut here ]------------^M^M >> [ 0.084018] WARNING: at >> /build/buildd-linux_3.2.21-3-i386-vEohn4/linux-3.2.21/arch/x86/xen/enlighten.c:738 >> perf_events_lapic_init+0x28/0x29()^M^M >> [ 0.088009] Hardware name: empty^M^M >> [ 0.091299] Modules linked in:^M^M >> [ 0.092275] Pid: 1, comm: swapper/0 Not tainted 3.2.0-3-686-pae #1^M^M >> [ 0.096008] Call Trace:^M^M >> [ 0.098527] [] ? warn_slowpath_common+0x68/0x79^M^M >> [ 0.100019] [] ? perf_events_lapic_init+0x28/0x29^M^M >> [ 0.104010] [] ? warn_slowpath_null+0xd/0x10^M^M >> [ 0.108011] [] ? perf_events_lapic_init+0x28/0x29^M^M >> [ 0.112015] [] ? init_hw_perf_events+0x223/0x3b1^M^M >> [ 0.116012] [] ? check_bugs+0x1d9/0x1d9^M^M >> [ 0.120012] [] ? do_one_initcall+0x66/0x10e^M^M >> [ 0.124012] [] ? kernel_init+0x6d/0x125^M^M >> [ 0.128012] [] ? start_kernel+0x325/0x325^M^M >> [ 0.132015] [] ? kernel_thread_helper+0x6/0x10^M^M >> [ 0.136019] ---[ end trace a7919e7f17c0a725 ]---^M^M >> -- snip -- >> >> And pretty soon degenerated into log message spamming of this sort: >> >> -- snip -- >> (XEN) traps.c:2584:d0 Domain attempted WRMSR 00000000c0010000 from >> 0x0000000000530076 to 0x0000000000130076.^M >> (XEN) traps.c:2584:d0 Domain attempted WRMSR 00000000c0010000 from >> 0x0000000000530076 to 0x0000000000130076.^M >> (XEN) traps.c:2584:d0 Domain attempted WRMSR 00000000c0010000 from >> 0x0000000000530076 to 0x0000000000130076.^M >> (XEN) traps.c:2584:d0 Domain attempted WRMSR 00000000c0010000 from >> 0x0000000000530076 to 0x0000000000130076.^M >> (XEN) traps.c:2584:d0 Domain attempted WRMSR 00000000c0010000 from >> 0x0000000000530076 to 0x0000000000130076.^M >> -- snip -- >> >> The serial log is attached ("exile.log"). >> >> An earlier kernel I had lying around, 2.6.32.25 (perhaps one of >> Jeremy's?) boots fine; the serial log is also attached >> ("exile-good.log"). It also seems ot have the WARN above, so maybe >> that's not actually the issue. >> >> Any ideas? > Implement the perf framework to work with Xen's oprofile, or make a new > set of hypercalls for it. > > The WARN can go away - its there to remind us to get it done at some point :-( OK, but is there a way I can actually get it to boot? I think the WRMSR is probably the real problem. -George