mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alok kataria" <alokkataria1@gmail.com>
To: tglx@linutronix.de, "Tetsuo Handa" <penguin-kernel@i-love.sakura.ne.jp>
Cc: akataria@vmware.com, devzero@web.de,
	linux-kernel@vger.kernel.org, dhecht@vmware.com
Subject: Re: Kernel hangs in SMP + VMware environment.
Date: Fri, 16 May 2008 22:59:47 -0700	[thread overview]
Message-ID: <35f686220805162259g18c6bcf9rf87103a98933cc94@mail.gmail.com> (raw)
In-Reply-To: <200805171034.CJC04647.HOFMOJVFQFOLtS@I-love.SAKURA.ne.jp>

On Fri, May 16, 2008 at 6:34 PM, Tetsuo Handa
<penguin-kernel@i-love.sakura.ne.jp> wrote:
> Alok Kataria wrote:
>> > I'm not sure, but this problem might exist in all kernels since 2.6.18 , for
>> > I can find clocksource= parameter in Documentation/kernel-parameters.txt .
>> >
>> Sorry, but I dont understand what you are pointing to, the 2.6.18 kernel does
>> have clocksource parameter.
>> And you are correct this could be a problem with all the kernels which are
>> using clocksource.
>>
>> If you are able to reproduce this with any of the kernels with the patch applied
>> Please let me know.
> I'm not saying "I was able to reproduce this problem after applying your patch".
> I'm saying "All kernels since 2.6.18 might have this problem, and we need to apply
> your patch to all kernels since 2.6.18 if they actually have this problem".
>> >

Thats correct, but I am not sure how the stable folks will pickup these patches.
Thomas, now if we need the patch in any previous  kernels stable tree
(in this instance 2.6.18.x), do we need to backport this patch for
each kernel (which shows this problem)  and send these patches to the
stable tree maintainers or is their some other way  ?
Sorry, but I am not aware of how the stable tree is maintained. Any
information regarding that would be helpful.

Thanks,
Alok

>> > The Ctrl-C didn't work, the Alt-F? didn't work, the Ctrl-Alt-Del didn't work.
>> > I had no time to reproduce it, so I'm not sure it has actually hanged up.
>> >
>
> Thanks.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

  reply	other threads:[~2008-05-17  5:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 18:30 Alok Kataria
2008-05-15  6:11 ` Tetsuo Handa
2008-05-15 19:44   ` Alok Kataria
2008-05-16 12:48     ` Tetsuo Handa
2008-05-17  1:22       ` Alok Kataria
2008-05-17  1:34         ` Tetsuo Handa
2008-05-17  5:59           ` Alok kataria [this message]
2008-05-17  7:16             ` Bart Van Assche
2008-06-27 12:34           ` Tetsuo Handa
2008-05-18 19:45 ` Jan Engelhardt
2008-05-20  1:08   ` Alok Kataria
  -- strict thread matches above, loose matches on Subject: below --
2008-05-13 18:05 Roland
2008-05-14 11:00 ` Tetsuo Handa
2008-05-12 21:41 Tetsuo Handa

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=35f686220805162259g18c6bcf9rf87103a98933cc94@mail.gmail.com \
    --to=alokkataria1@gmail.com \
    --cc=akataria@vmware.com \
    --cc=devzero@web.de \
    --cc=dhecht@vmware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®