From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Fiala Subject: Re: Xen 4.2.1, linux kernel 3.7.5 crashed while reboot Date: Tue, 26 Feb 2013 17:40:33 +0100 Message-ID: <512CE581.7020308@mfiala.net> References: <512CC78B.4080606@mfiala.net> <512CEB5C02000078000C1272@nat28.tlf.novell.com> <512CE2C6.3040907@mfiala.net> <512CF1E702000078000C12C7@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <512CF1E702000078000C12C7@nat28.tlf.novell.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: Jan Beulich Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 02/26/2013 05:33 PM, Jan Beulich wrote: >>>> On 26.02.13 at 17:28, Michal Fiala 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? > > Jan > >> On 02/26/2013 05:05 PM, Jan Beulich wrote: >>>>>> On 26.02.13 at 15:32, Michal Fiala wrote: >>>> I have updated system to xen 4.2.1, linux kernel 3.7.5. System boots >>>> without problem. When I run reboot or shutdown -r now, system correctly >>>> shutdowns all runlevels and then system crashed, see crash_output.txt. >>>> I have the same problem with kernel linux 3.2.37. When I shudown system >>>> (halt), then it is without problem. I have tested kernel 3.7.5 without >>>> xen hypervisor, it was without problems. Required debug informations >>>> (http://wiki.xen.org/wiki/XenParavirtOpsHelp) in attachment. >>>> Could you please help me with this problem? >>> >>> It's apparently going the triple fault path, and load_idt() under Xen >>> doesn't do what the code here expects (i.e. that reboot method >>> just can't work under Xen). Are you overriding the reboot type on >>> the kernel command line? >>> >>> Jan >>> > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >