From: bostik@bostik.iki.fi (Mika Bostrom)
To: Nathan Scott <nathans@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS=n
Date: Thu, 29 Jul 2004 18:42:24 +0300 [thread overview]
Message-ID: <20040729154224.GA3030@bostik.iki.fi> (raw)
In-Reply-To: <20040729060900.GA1946@frodo>
[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]
On Thu, Jul 29, 2004 at 04:09:00PM +1000, Nathan Scott wrote:
> On Tue, Jul 20, 2004 at 09:50:12PM +0200, Adrian Bunk wrote:
> > Mark this combination as BROKEN until XFS is fixed.
> This part is not useful. We want to hear about problems
> that people hit with 4K stacks so we can try to address
> them, and it mostly works as is.
I can mention one. This is not a bugreport (yet).
I can reproduce a complete hard-lock on 2.6.7 vanilla with the
following setup:
* VMWare 4.5.2 (taints kernel, I know)
* NIC is bridged
* XFS filesystem
* 4k stacks
Inside vmware, I am running an instance of modified OpenBSD. With 4k
stacks, at least once a day the system locks hard. The shortest time
between two forced boots was about 20 minutes.
The hang is triggered everytime by a single instance: guest OS sends a
DHCP-request, and this causes the linux kernel to hang. This does not
happen every time, but perhaps every fourth or fifth time. On one
occasion, it was the first time immediately after boot.
Compiling 2.6.7 with 8k stacks has so far solved this issue. No random
hangs.
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.
--
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 --]
next prev parent reply other threads:[~2004-07-29 15:47 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 ` Mika Bostrom [this message]
2004-07-29 16:09 ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS=n Zwane Mwaikambo
2004-07-29 16:36 ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS Mika Bostrom
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=20040729154224.GA3030@bostik.iki.fi \
--to=bostik@bostik.iki.fi \
--cc=bostik+lkml@bostik.iki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
/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.