Re: Failure to boot default Debian wheezy (pvops) kernel on 4.2-rc2

[Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>]

On Fri, Aug 17, 2012 at 02:18:19PM +0100, George Dunlap wrote:
> 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]  [<c1037fcc>] ? warn_slowpath_common+0x68/0x79^M^M
> >>[    0.100019]  [<c10150d2>] ? perf_events_lapic_init+0x28/0x29^M^M
> >>[    0.104010]  [<c1037fea>] ? warn_slowpath_null+0xd/0x10^M^M
> >>[    0.108011]  [<c10150d2>] ? perf_events_lapic_init+0x28/0x29^M^M
> >>[    0.112015]  [<c141c97e>] ? init_hw_perf_events+0x223/0x3b1^M^M
> >>[    0.116012]  [<c141c75b>] ? check_bugs+0x1d9/0x1d9^M^M
> >>[    0.120012]  [<c1003074>] ? do_one_initcall+0x66/0x10e^M^M
> >>[    0.124012]  [<c1415770>] ? kernel_init+0x6d/0x125^M^M
> >>[    0.128012]  [<c1415703>] ? start_kernel+0x325/0x325^M^M
> >>[    0.132015]  [<c12c463e>] ? 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.

It should have no trouble booting? The WRMSR are the perf counters that are
being tested (I think)

Oh, maybe not. I wonder if those are the APERF? So the scheduler has some
code to probe the MSRS, This git commit: d95a8d4b876b60ce8497fc3216d06823c492bba6
takes care of that.

But that should show up 3.2 kernel? Not there?

> 
>  -George