From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Xen 4.2.1, linux kernel 3.7.5 crashed while reboot
Date: Tue, 26 Feb 2013 17:01:00 -0500
Message-ID: <20130226220100.GA22418@phenom.dumpdata.com>
References: <512CC78B.4080606@mfiala.net>
	<512CEB5C02000078000C1272@nat28.tlf.novell.com>
	<512CE2C6.3040907@mfiala.net>
	<512CF1E702000078000C12C7@nat28.tlf.novell.com>
	<512CE581.7020308@mfiala.net>
	<512CF62C02000078000C12F1@nat28.tlf.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <512CF62C02000078000C12F1@nat28.tlf.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>
Cc: Michal Fiala <fiala@mfiala.net>, xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

On Tue, Feb 26, 2013 at 04:51:39PM +0000, Jan Beulich wrote:
> >>> On 26.02.13 at 17:40, Michal Fiala <fiala@mfiala.net> wrote:
> > On 02/26/2013 05:33 PM, Jan Beulich wrote:
> >>>>> On 26.02.13 at 17:28, Michal Fiala <fiala@mfiala.net> 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@lists.xen.org
> http://lists.xen.org/xen-devel
>