All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Barazer <gabriel@oxeva.fr>
To: linux-kernel@vger.kernel.org
Subject: 2.6.22 x86_64 : kernel initial decompression hangs on vmware
Date: Thu, 26 Jul 2007 02:08:38 +0200	[thread overview]
Message-ID: <46A7E606.4030001@oxeva.fr> (raw)

Hi,

After upgrading kernel to 2.6.22 on a Vmware workstation guest version 
5.5 and 6 , the kernel decompression stage ("Decompressing Linux...") is 
hanging for a very long time (~5 minutes) before finally  succeeding 
(displaying "done.\nBooting the kernel.\n"). During this time, the VM 
process is eating all the CPU time during the decompression, like an 
infinite loop.
Between these 2 strings is the gunzip() function at 
boot/compressed/misc.c which does the real job, and the problem seemed 
to appear since commit 1ab60e0f72f71ec54831e525a3e1154f1c092408. 
(2.6.22-rc1 hangs, 2.6.21.6 works). The problem occurs with or without 
CONFIG_RELOCATABLE enabled.

What are the possible solutions to confirm where the problem is coming 
from ?

Thanks,

Gabriel

             reply	other threads:[~2007-07-26  0:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26  0:08 Gabriel Barazer [this message]
2007-07-26  0:19 ` 2.6.22 x86_64 : kernel initial decompression hangs on vmware Zachary Amsden
     [not found] ` <46A7E606.4030001-KSe8qvLY914@public.gmane.org>
2007-08-04 16:23   ` Zachary Amsden
2007-08-04 16:23     ` Zachary Amsden
     [not found]     ` <46B4A7E4.4030907-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
2007-08-04 17:18       ` Gabriel Barazer
2007-08-04 17:18         ` Gabriel Barazer
2007-08-09 20:57       ` Avi Kivity
2007-08-09 20:57         ` Avi Kivity
     [not found]         ` <46BB7FCC.4040509-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-09 23:28           ` Zachary Amsden
2007-08-09 23:28             ` Zachary Amsden
2007-08-10  1:48             ` Avi Kivity

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=46A7E606.4030001@oxeva.fr \
    --to=gabriel@oxeva.fr \
    --cc=linux-kernel@vger.kernel.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.