From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Thomas Lenherr <thomas@lenherr.name>
Cc: linux-smp@vger.kernel.org
Subject: Re: Problems with SMP
Date: Thu, 28 Oct 2004 08:13:18 -0700 [thread overview]
Message-ID: <41810C8E.3010708@osdl.org> (raw)
In-Reply-To: <4180FC04.4010800@lenherr.name>
Thomas Lenherr wrote:
> Hi,
> I'm using an Asus PC-DL and everything works fine, except I'm
> experiencing troubles when copying files via a network fs (nfs and smb).
> Because of that I wrote to the linux-fsdevel-list and to the lkml.
> A exact description of the symptons may be read here:
> http://bugme.osdl.org/show_bug.cgi?id=3608
>
> My system had 2 P4 with HT activated, but a few days ago I deactivated
> HT and instantly I experienced much less troubles (~2/9 files corrupted
> via nfs instead of ~7/9). After this I compiled a kernel without
> smp-support and the problem was gone. Got no more any corrupted files!
> It's a bit weird that I got only troubles with network filesystems, but
> that's the way it is ...
> Please read the description given in the bug-report link given above for
> further informations, but, as I said, when I posted this bug I hadn't
> realized yet it got something to do with smp...
>
> I'd be very pleased if somebody could help me so that I could reactivate
> my second processor :)
You probably don't want to go thru the corruption again,
but can you tell us if this happens with CONFIG_PREEMPT=y or n?
There have been a few problems recently with PREEMPT not being
used safely. If it happens with PREEMPT=y, can you test it
with PREEMPT=n please.
--
~Randy
next prev parent reply other threads:[~2004-10-28 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 14:02 Problems with SMP Thomas Lenherr
2004-10-28 15:13 ` Randy.Dunlap [this message]
2004-10-28 18:23 ` Thomas Lenherr
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=41810C8E.3010708@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-smp@vger.kernel.org \
--cc=thomas@lenherr.name \
/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