linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: virtualization@lists.linux-foundation.org,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: v3.18-rc1 32 bit KVM hangs early in boot process
Date: Fri, 24 Oct 2014 17:44:45 +0200	[thread overview]
Message-ID: <544A73ED.3080106@gmx.de> (raw)
In-Reply-To: <CA+5PVA5MCRhwnkbNXpMmLzeM4G=aau0kuRU_wma-5T59M+2vkA@mail.gmail.com>

On 10/21/2014 06:40 PM, Josh Boyer wrote:
> On Tue, Oct 21, 2014 at 12:10 PM, Toralf Förster <toralf.foerster@gmx.de> wrote:
>> On 10/20/2014 07:34 PM, Toralf Förster wrote:
>>> I uploaded the screen shots from the virt-manager to [1] and [2]
>>>
>>> FWIW e56d9fccb was fine so the bug slipped in after that.
>>>
>>
>>>
>>> [1] http://www.directupload.net/file/d/3781/j9mwrtpq_jpg.htm
>>> [2] http://www.directupload.net/file/d/3781/29trc56v_jpg.htm
>>>
>> It might be virtio-console related, when the uevetns are processed:
>>
>> http://www.directupload.net/file/d/3782/6lg5yihh_jpg.htm
> 
> Try
> http://mid.gmane.org/1413813529-11044-1-git-send-email-cornelia.huck@de.ibm.com
> 
> josh
> 
I just reverted

$ grep commit virtcons_*
virtcons_1.patch:commit f5866db64f341776c2d9ed48080f82459fea6a55
virtcons_2.patch:commit 401bbdc901b268113d7c562616feb7fc37492aca

on top of -rc1 which solved the issue entirely here.


-- 
Toralf
pgp key: 0076 E94E


  parent reply	other threads:[~2014-10-24 15:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20 17:34 v3.18-rc1 32 bit KVM hangs early in boot process Toralf Förster
2014-10-20 17:59 ` Josh Boyer
2014-10-21 16:10 ` Toralf Förster
2014-10-21 16:40   ` Josh Boyer
2014-10-21 17:31     ` Toralf Förster
2014-10-24 15:44     ` Toralf Förster [this message]
2014-10-24 16:00       ` Toralf Förster

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=544A73ED.3080106@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=jwboyer@fedoraproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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).