Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Thu, Apr 08, 2010 at 01:34:22PM +0200, Thomas Schwinge wrote:
> Hello!
> 
> This was originally reported to the Debian BTS,
> <http://bugs.debian.org/576877>, but Ian Campbell suggested to forward it
> to xen-devel.

Nice writeup. I like how you included all the details that I would have
thought of to ask. Is this the normal Debian bug reporting procedure ?
> 
> 
> To get the Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 kernel to
> boot, I need to supply mem=4G.  This was not necessary with the 2.6.32-10
> kernel.
> 
> I only changed the kernel, no further changes.
> 
> 2.6.32-11 is ``based on commit f64df18aae5ab07b44bdcc2334cf0044ef46320c
> of git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git.'' --
> according to debian/patches/features/all/xen/pvops.patch.
> 
> commit f64df18aae5ab07b44bdcc2334cf0044ef46320c
> Merge: d945b01 d69a8da
> Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>
> Date:   Thu Mar 25 17:00:21 2010 -0700
> 
>     Merge commit 'd69a8da4f6f2bb1815d2bc2f49afed3f3ee4f07d' into 
> xen/stable-2.6.32.x
>     
>     * commit 'd69a8da4f6f2bb1815d2bc2f49afed3f3ee4f07d':
>       xen/apic: Don't register GSI in pre-setup
>       xen/apic: Map physical interrupt before setting up GSI
>       xen/apic: Control-flow cleanup in xen_register_gsi
> 
> 
> The noreboot and nopat options that Ian suggested in
> <http://bugs.debian.org/576877#10> have no effect.  (I always have
> noreboot specified.)

OK. Then the next thing that comes in my mind is ACPI GSI. For that
thought we will need ...

> 
> 
> 2.6.32-10:
>     (XEN) Xen version 3.4 (Debian 3.4.3~rc3-1) (waldi@xxxxxxxxxx) (gcc 
> version 4.4.3 (Debian 4.4.3-2) ) Mon Mar  1 21:16:18 UTC 2010
>     (XEN) Command line: 
>     (XEN) Video information:
>     (XEN)  VGA is text mode 80x25, font 8x16
>     (XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
>     (XEN) Disc information:
>     (XEN)  Found 1 MBR signatures
>     (XEN)  Found 1 EDD information structures
>     (XEN) Xen-e820 RAM map:
>     (XEN)  0000000000000000 - 000000000009e000 (usable)
>     (XEN)  000000000009e000 - 00000000000a0000 (reserved)
>     (XEN)  00000000000e4000 - 0000000000100000 (reserved)
>     (XEN)  0000000000100000 - 00000000ddee0000 (usable)
>     (XEN)  00000000ddee0000 - 00000000ddeef000 (ACPI data)
>     (XEN)  00000000ddeef000 - 00000000ddf00000 (ACPI NVS)
>     (XEN)  00000000ddf00000 - 00000000e0000000 (reserved)
>     (XEN)  00000000fec00000 - 00000000fec10000 (reserved)
>     (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
>     (XEN)  00000000fff00000 - 0000000100000000 (reserved)
>     (XEN)  0000000100000000 - 0000000120000000 (usable)
>     (XEN) System RAM: 4062MB (4159992kB)
> 
> 2.6.32-11: resets the machine immediatelly, no log messages visible
> (don't have serial console set-up).


.. we need to see more of what Xen and Linux prints during bootup
which can be done by adding these in the Xen command line: 
"loglvl=all guest_loglvl=all sync_console console_to_ring apic=debug
apic_verbosity=debug" (the kitchensink of all the debug options on)
and this in the Linux kernel line: "console=hvc0 earlyprintk=xen debug
initcall_debug acpi.debug_level=0xffffffff acpi.debug_layer=0x2"

You might get away without a serial console and see the output on the
display. But it would be much much better to get the serial console
working. Pasi wrote an excellent Wiki page explaining how to do this:
http://wiki.xensource.com/xenwiki/XenSerialConsole

Please e-mail back the full serial console or the last thing you see on the VGA 
screen.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel