Re: [Xen-devel] Xen 4.2.1, linux kernel 3.7.5 crashed while reboot

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

On Tue, Feb 26, 2013 at 04:51:39PM +0000, Jan Beulich wrote:
> >>> On 26.02.13 at 17:40, Michal Fiala <fiala@xxxxxxxxxx> wrote:
> > On 02/26/2013 05:33 PM, Jan Beulich wrote:
> >>>>> On 26.02.13 at 17:28, Michal Fiala <fiala@xxxxxxxxxx> wrote:
> >> 
> >> Please don't top post.
> >> 
> >>> The kernel command line from grub.conf
> >>>
> >>> kernel /xen.gz dom0_mem=4G,max:4G dom0_max_vcpus=4 dom0_vcpus_pin
> >>> console=com2,vga com2=115200,8n1
> >>> module /linux-3.7.5-hardened root=/dev/sda6 console=tty0 console=hvc0
> >>>
> >>> I have not modified reboot type.
> >> 
> >> And did you check your full boot log for an info-level message like
> >> 
> >> "%s series board detected. Selecting %s-method for reboot.\n"
> > 
> > I have only checked normal boot log, see attachment in my first mail.
> > How can I enable info-level message?
> 
> Looks like this has info level messages enabled, and I can't see any
> such message there. So I guess you'll have to add a few printk()-s
> to arch/x86/kernel/reboot.c:native_machine_emergency_restart().

The thing is is that native_machine_emergency_restart is not suppose
to be called. The baremetal machine_ops has that, but we over-write
it with our own and he should get:

         .emergency_restart = xen_emergency_restart,

! So how did his .emergency_restart value get over-written by
native_machine_emergency_restart?

> 
> Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel