From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Lenherr Subject: Problems with SMP Date: Thu, 28 Oct 2004 16:02:44 +0200 Sender: linux-smp-owner@vger.kernel.org Message-ID: <4180FC04.4010800@lenherr.name> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig5BA1FDC87EED4697E6AF651C" Return-path: List-Id: To: linux-smp@vger.kernel.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5BA1FDC87EED4697E6AF651C Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 :) Thanks in advance, Thomas Lenherr --------------enig5BA1FDC87EED4697E6AF651C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBgPwI3E1pPHX30VoRAlZQAJ0Uitifea8pIH0fYR24MFBPS9srMgCaAg6+ qXYiBIjHDhHB+BWXcrO3T4Q= =RuzD -----END PGP SIGNATURE----- --------------enig5BA1FDC87EED4697E6AF651C--