All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Haigh <netwiz@crc.id.au>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
	Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: vnc=1 / pvgrub / close fb: backend at /local/domain/0/backend/vfb/xx/0
Date: Thu, 06 Nov 2014 20:49:16 +1100	[thread overview]
Message-ID: <545B441C.9040907@crc.id.au> (raw)
In-Reply-To: <alpine.DEB.2.02.1411051645140.22875@kaball.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 2808 bytes --]

Hi Stefano,

It seems that this patch fixes the grub issue for me. I no longer get
the infinite wait at the grub prompt.

On 6/11/2014 4:49 AM, Stefano Stabellini wrote:
> Hello Steven,
> I have found some time to debug this myself.
> I couldn't reproduce the booting issue that you reported: in my case
> after seeing the grub boot menu I can successfully boot the kernel
> without problems.
> 
> However I can reproduce the timeout issue that you are seeing: the
> timeout doesn't work properly in graphics mode.
> 
> The reason is that the with a graphics terminal you checkkey () return 0
> even when pressing no keys, resulting in wrong behaviour in run_menu. 
> 
> Does the following patch (also attached) fixes your issues?
> 
> 
> diff --git a/stubdom/grub.patches/11graphics-keyboard.diff b/stubdom/grub.patches/11graphics-keyboard.diff
> new file mode 100644
> index 0000000..fe17b20
> --- /dev/null
> +++ b/stubdom/grub.patches/11graphics-keyboard.diff
> @@ -0,0 +1,13 @@
> +diff --git a/stage2/stage2.c b/stage2/stage2.c
> +index 9d9fcc3..8353a3b 100644
> +--- a/stage2/stage2.c
> ++++ b/stage2/stage2.c
> +@@ -395,7 +395,7 @@ restart:
> + 	 pressed.  
> + 	 This avoids polling (relevant in the grub-shell and later on
> + 	 in grub if interrupt driven I/O is done).  */
> +-      if (checkkey () >= 0 || grub_timeout < 0)
> ++      if (checkkey () > 0 || grub_timeout < 0)
> + 	{
> + 	  /* Key was pressed, show which entry is selected before GETKEY,
> + 	     since we're comming in here also on GRUB_TIMEOUT == -1 and
> 
> 
> 
> On Thu, 23 Oct 2014, Steven Haigh wrote:
>> On 23/10/2014 2:40 AM, Ian Campbell wrote:
>>> On Thu, 2014-10-23 at 02:23 +1100, Steven Haigh wrote:
>>>
>>>> Output using pv-grub:
>>>
>>> Can you also post the qemu logs please (under /var/log/xen somewhere I
>>> think).
>>
>> I get very little out of this:
>> -rw-r--r--  1 root root    0 Oct 23 02:45 qemu-dm-dev.vm.log
>> -rw-r--r--  1 root root    0 Oct 23 02:44 xen-hotplug.log
>> -rw-r--r--  1 root root   55 Oct 23 02:45 xl-dev.vm.log
>> [root@dom0 xen]# cat xl-dev.vm.log
>> Waiting for domain dev.vm (domid 36) to die [pid 6970]
>>
>> That's it :\
>>
>>>> qemu-system-i38[3956]: segfault at 0 ip           (null) sp
>>>> 00007fffb4573638 error 4
>>>
>>> That might be a smoking gun. Is there a core dump and/or could you try
>>> and run qemu under gdb?
>>
>> Any hints on doing this? I can't say I'm a gdb guru.... I can't find any
>> core dumps anywhere so that's not really helpful...
>>
>> -- 
>> Steven Haigh
>>
>> Email: netwiz@crc.id.au
>> Web: http://www.crc.id.au
>> Phone: (03) 9001 6090 - 0412 935 897
>>

-- 
Steven Haigh

Email: netwiz@crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 834 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

  reply	other threads:[~2014-11-06  9:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 15:17 vnc=1 / pvgrub / close fb: backend at /local/domain/0/backend/vfb/xx/0 Steven Haigh
2014-10-21 21:24 ` Steven Haigh
2014-10-22  9:00   ` Ian Campbell
2014-10-22  9:59     ` Samuel Thibault
2014-10-22 10:10       ` Steven Haigh
2014-10-22 10:19         ` Samuel Thibault
2014-10-22 10:31         ` Ian Campbell
2014-10-22 10:45           ` Steven Haigh
2014-10-22 10:40       ` Ian Campbell
2014-10-22 11:57         ` Stefano Stabellini
2014-10-22 12:05           ` Ian Campbell
2014-10-22 12:13             ` Stefano Stabellini
2014-10-22 15:23               ` Steven Haigh
2014-10-22 15:40                 ` Ian Campbell
2014-10-22 15:53                   ` Steven Haigh
2014-10-23  8:21                     ` Ian Campbell
2014-11-05 17:49                     ` Stefano Stabellini
2014-11-06  9:49                       ` Steven Haigh [this message]
2014-11-06 10:34                         ` Stefano Stabellini
2014-11-06 11:05                           ` Steven Haigh
2014-11-06 10:41                     ` [PATCH] pvgrub: ignore NUL Stefano Stabellini
2014-11-06 11:39                       ` Samuel Thibault
2014-11-06 15:43                         ` Stefano Stabellini
2014-11-06 19:36                           ` Konrad Rzeszutek Wilk
2014-11-06 23:13                             ` Samuel Thibault
2014-11-10 12:20                         ` Ian Campbell
2014-11-10 12:21                         ` Ian Campbell

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=545B441C.9040907@crc.id.au \
    --to=netwiz@crc.id.au \
    --cc=Ian.Campbell@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=stefano.stabellini@eu.citrix.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.