All of lore.kernel.org
 help / color / mirror / Atom feed
From: bostik@bostik.iki.fi (Mika Bostrom)
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Mika Bostrom <bostik+lkml@bostik.iki.fi>,
	Nathan Scott <nathans@sgi.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS
Date: Thu, 29 Jul 2004 19:36:01 +0300	[thread overview]
Message-ID: <20040729163601.GA3308@bostik.iki.fi> (raw)
In-Reply-To: <Pine.LNX.4.58.0407291205590.8976@montezuma.fsmlabs.com>

[-- Attachment #1: Type: text/plain, Size: 2018 bytes --]

On Thu, Jul 29, 2004 at 12:09:29PM -0400, Zwane Mwaikambo wrote:
> On Thu, 29 Jul 2004, Mika Bostrom wrote:
> 
> >   Now, the reason this can't be any kind of bugreport is clear:
> >   1) kernel is tainted
> >   2) VMWare's modules are not yet updated to cope with 2.6.7 kernel
> >
> >   So until VMWare updates their product, I consider this a bug in their
> > modules. When they do, I intend to test 4k stacks again. If the hangs
> > continue, then I shall see with their support whether it can be tracked
> > to their code or not.
> >
> >   But at least at the moment if you wish to use VMWare and XFS, using 4k
> > stacks is, in my experience, asking for trouble.
> 
> Given that XFS and 4k stacks has known issues perhaps it isn't a fault of
> VMWare. I've been using VMWare 4 with 4K stacks running linux, netbsd and
> win2k on a system with a 30day uptime, i'm using ext3 on 2.6.7-rc3-mm2.

  Quite true, and a good point. However, this is one case that can be
reproduced - not systematically, but with certainty - and which displays
a clear difference between 4k and 8k stacks. Enabling noisy debugs and
tagging on a serial console might catch something. 

  My co-worker uses a FC2 stock kernel and I remember someone from RH
(Ingo Molnar?) saying that those are currently built with 4k stacks.  He
has had no such troubles, but then, he isn't using XFS.

  I'm merely providing this as an additional info for those who assume
that VMWare knows what they are doing and wish to start debugging the
combination sooner rather than later. (Even if 'later' proves to
eliminate some dead-end test-case scenarios.) Nathan Scott explicitly
requested for information on troublesome setups, so one could say I'm
humouring him and granting a wish, of a sort :)

-- 
 Mika Boström      +358-40-525-7347  \-/  "World peace will be achieved
 Bostik@iki.fi    www.iki.fi/bostik   X    when the last man has killed
 Security freak, and proud of it.    /-\   the second-to-last." -anon?

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-07-29 16:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-20 11:44 4K stack kernel get Oops in Filesystem stress test Cahya Wirawan
2004-07-20 12:04 ` Steve Lord
2004-07-20 14:39   ` Jeffrey E. Hundstad
2004-07-20 19:50     ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS=n Adrian Bunk
2004-07-20 20:42       ` Chris Wedgwood
2004-07-20 20:50         ` Adrian Bunk
2004-07-20 20:58           ` Chris Wedgwood
2004-07-29  6:09       ` Nathan Scott
2004-07-29 11:42         ` Adrian Bunk
2004-07-29 11:46           ` Arjan van de Ven
2004-07-29 21:11             ` Adrian Bunk
2004-07-29 21:44               ` Chris Wedgwood
2004-07-29 22:30           ` [xfs-masters] " Nathan Scott
2004-08-01 19:02             ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL Adrian Bunk
2004-07-29 15:42         ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS=n Mika Bostrom
2004-07-29 16:09           ` Zwane Mwaikambo
2004-07-29 16:36             ` Mika Bostrom [this message]
2004-07-22  7:27     ` 4K stack kernel get Oops in Filesystem stress test Amon Ott
2004-07-29  2:14       ` Nathan Scott

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=20040729163601.GA3308@bostik.iki.fi \
    --to=bostik@bostik.iki.fi \
    --cc=bostik+lkml@bostik.iki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathans@sgi.com \
    --cc=zwane@linuxpower.ca \
    /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.