From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Harmandeep Kaur <write.harmandeep@gmail.com>
Cc: xen-devel@lists.xenproject.org,
Dario Faggioli <dario.faggioli@citrix.com>
Subject: Re: Blank screen while booting xen
Date: Mon, 11 Jan 2016 09:53:30 -0500 [thread overview]
Message-ID: <20160111145330.GA10641@char.us.oracle.com> (raw)
In-Reply-To: <CAPtdW140ECgKXJzV-TYCMfk+q8j68aJHOYeAFtzi77QE6y7=FQ@mail.gmail.com>
On Mon, Jan 11, 2016 at 12:57:27AM +0530, Harmandeep Kaur wrote:
> Hi,
>
> I tried to modify and compile some of Xen 4.7's code
> (cloned from git clone git://xenbits.xen.org/xen.git)
> and even with a very minor change (patch included at last)
> my xen failed to boot. It stucks at black blank screen after
> showing some xen logs.
What is on your Linux command line? Do you have 'console=hvc0' ?
>
> By adding "vga=text-80x80,keep" to the grub before booting
> xen., infinite loop of text
> "(XEN) traps.c:3290: GPF (0000): ffff82d0801af4d5 -> ffff82d080240e5a"
> appears.
>
> I tried to compile and boot xen reverting the change, but
> same issue still exists.
>
> Also I tried to setup serial console but my output is garbled.
> More info on it here,
> http://lists.xenproject.org/archives/html/xen-devel/2015-12/msg02045.html
>
> I tried different software (cu, gtkterm), different baud rates,
> different serial-USB cable and stopping modemmanager,
> but no luck.
How did you set the baudrate? I usually do 'screen /dev/ttyUSB0 115200 cs8'
?
>
> I am using i3-6100 processor, if that info is needed.I will
> appreciate any help.
dmesg | grep tty
and lspci
could also help?
>
> Regards,
> Harmandeep Kaur
> Outreachy Intern
>
> -----------------------------------------------PATCH---------------------------------------------
> >From c814c4ac0028bdef0082561ad6cd69570502c3ba Mon Sep 17 00:00:00 2001
> From: Harmandeep Kaur <write.harmandeep@gmail.com>
> Date: Tue, 29 Dec 2015 22:23:21 +0530
> Subject: [PATCH] First mod
>
> Signed-off-by: Harmandeep Kaur <write.harmandeep@gmail.com>
> ---
> xen/common/sched_credit.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/xen/common/sched_credit.c b/xen/common/sched_credit.c
> index 0dce790..b395501 100644
> --- a/xen/common/sched_credit.c
> +++ b/xen/common/sched_credit.c
> @@ -1148,6 +1148,8 @@ csched_dom_init(const struct scheduler *ops,
> struct domain *dom)
> {
> struct csched_dom *sdom;
>
> +printk("XXX Hello, this is my first mod :) \n");
> +
> if ( is_idle_domain(dom) )
> return 0;
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-11 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-10 19:27 Blank screen while booting xen Harmandeep Kaur
2016-01-11 14:53 ` Konrad Rzeszutek Wilk [this message]
2016-01-11 17:26 ` Harmandeep Kaur
2016-01-11 17:30 ` Konrad Rzeszutek Wilk
2016-01-11 17:45 ` Harmandeep Kaur
2016-01-11 18:06 ` Konrad Rzeszutek Wilk
2016-01-14 14:03 ` 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=20160111145330.GA10641@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=dario.faggioli@citrix.com \
--cc=write.harmandeep@gmail.com \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).