All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harmandeep Kaur <write.harmandeep@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	xen-devel@lists.xen.org, Shuai Ruan <shuai.ruan@linux.intel.com>
Subject: Re: Error booting Xen
Date: Tue, 26 Jan 2016 23:32:50 +0530	[thread overview]
Message-ID: <CAPtdW15JcNEHhS+Ykt63WV_Zrx_yGHK=v89coHD0Rip5QChtiQ@mail.gmail.com> (raw)
In-Reply-To: <56A7B98C02000078000CB3B8@prv-mh.provo.novell.com>

Last time, I did absolutely nothing. System was idle
and it crashed just after the login. Now, I booted the
system again and this time, there is no reset. But,
performance of the system is very slow. Browser
(Mozilla Firefox) freezes a lot. Also, before applying
patches, when I used to disabe xsave it resulted in
same kind of performance issues. And the following
is still present in the log.

(XEN) traps.c:3290: GPF (0000): ffff82d0801c1cea -> ffff82d080252e5c
(XEN) d1v1 fault#1: mxcsr=00001f80
(XEN) d1v1 xs=0000000000000003 xc=8000000000000000
(XEN) d1v1 r0=0000000000000000 r1=0000000000000000
(XEN) d1v1 r2=0000000000000000 r3=0000000000000000
(XEN) d1v1 r4=0000000000000000 r5=0000000000000000
(XEN) traps.c:3290: GPF (0000): ffff82d0801c1cea -> ffff82d080252e5c
(XEN) d1v1 fault#2: mxcsr=00001f80
(XEN) d1v1 xs=0000000000000000 xc=0000000000000000
(XEN) d1v1 r0=0000000000000000 r1=0000000000000000
(XEN) d1v1 r2=0000000000000000 r3=0000000000000000
(XEN) d1v1 r4=0000000000000000 r5=0000000000000000

Full log here: http://paste2.org/C8WpyKOg

Regards,
Harmandeep

On Tue, Jan 26, 2016 at 10:53 PM, Jan Beulich <JBeulich@suse.com> wrote:
>>>> On 26.01.16 at 18:01, <write.harmandeep@gmail.com> wrote:
>> I tried 3rd patch together with earlier two. I'm
>> afraid the problem is not solved completely.
>> Full log goes here, http://paste2.org/KEAetMHb
>
> Well, wait - we can't solve all problems at once. The crash here
> is in the context of do_domctl(), i.e. makes me assume that the
> system booted up fine (and the problematic log messages are
> gone). So the original issue is fixed. Now for this second issue,
> would you mind first of all telling us what exactly it is you're
> doing when the crash occurs? Because, as you hopefully
> understand, such information often helps understanding where
> and/or why things are going wrong.
>
> Jan
>

  reply	other threads:[~2016-01-26 18:02 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 18:03 Error booting Xen Harmandeep Kaur
2016-01-18 18:09 ` Andrew Cooper
2016-01-18 18:29   ` Dario Faggioli
2016-01-19 13:36     ` Jan Beulich
2016-01-19 14:51       ` Dario Faggioli
2016-01-19 15:07         ` Andrew Cooper
2016-01-19 16:27           ` Harmandeep Kaur
2016-01-19 16:47             ` Jan Beulich
2016-01-19 17:02               ` Andrew Cooper
2016-01-19 17:08                 ` Dario Faggioli
2016-01-19 17:09                   ` Andrew Cooper
2016-01-19 19:55                   ` Harmandeep Kaur
2016-01-20 10:06                     ` Jan Beulich
2016-01-21 15:14                       ` Dario Faggioli
2016-01-21 15:24                         ` Harmandeep Kaur
2016-01-25 13:42                         ` Jan Beulich
2016-01-26 11:58                           ` Dario Faggioli
2016-01-26 12:51                           ` Harmandeep Kaur
2016-01-26 13:13                             ` Harmandeep Kaur
2016-01-26 13:23                               ` Jan Beulich
2016-01-26 17:01                                 ` Harmandeep Kaur
2016-01-26 17:23                                   ` Jan Beulich
2016-01-26 18:02                                     ` Harmandeep Kaur [this message]
2016-01-26 18:28                                       ` Dario Faggioli
2016-01-26 18:36                                         ` Harmandeep Kaur
2016-01-27  8:24                                       ` Jan Beulich
2016-01-27 13:12                                       ` Jan Beulich
2016-01-27 13:28                                         ` Harmandeep Kaur
2016-01-27 14:28                                           ` Jan Beulich
2016-01-28 19:17                                             ` Harmandeep Kaur
2016-01-29 10:13                                               ` Jan Beulich
2016-02-03  8:23                                                 ` Dario Faggioli
2016-02-03 11:35                                                   ` Harmandeep Kaur
2016-02-03 12:49                                                     ` Jan Beulich
2016-02-03 12:55                                                     ` Dario Faggioli
2016-02-03 13:10                                                       ` Andrew Cooper
2016-02-03 13:17                                                         ` Dario Faggioli
2016-02-03 16:57                                                           ` Konrad Rzeszutek Wilk
2016-02-03 13:40                                                       ` Harmandeep Kaur
2016-02-03 14:18                                                         ` Jan Beulich
2016-01-26 13:22                             ` Jan Beulich
2016-02-02  4:43                       ` Shuai Ruan
     [not found]                       ` <20160202044349.GA3036@shuai.ruan@linux.intel.com>
2016-02-02 10:39                         ` Andrew Cooper
2016-02-03  0:56                           ` Shuai Ruan
2016-02-03  7:56                           ` Shuai Ruan
2016-01-19 14:07 ` Harmandeep Kaur

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPtdW15JcNEHhS+Ykt63WV_Zrx_yGHK=v89coHD0Rip5QChtiQ@mail.gmail.com' \
    --to=write.harmandeep@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=shuai.ruan@linux.intel.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.