From owner-freebsd-stable@FreeBSD.ORG Sat Oct 24 14:36:53 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F83C1065692 for ; Sat, 24 Oct 2009 14:36:53 +0000 (UTC) (envelope-from jbozza@mindsites.com) Received: from mail.thinkburst.com (mail.thinkburst.com [204.49.104.46]) by mx1.freebsd.org (Postfix) with ESMTP id 50A218FC17 for ; Sat, 24 Oct 2009 14:36:53 +0000 (UTC) Received: from mailgate.mindsites.net (gateway.mindsites.net [204.49.104.36]) by mail.thinkburst.com (Postfix) with ESMTP id 8ACF51CC5E; Sat, 24 Oct 2009 09:36:52 -0500 (CDT) Received: from remote.mindsites.com (unknown [10.1.1.5]) by mailgate.mindsites.net (Postfix) with ESMTP id 62D6017040; Sat, 24 Oct 2009 09:36:52 -0500 (CDT) Received: from ATLAS.msg.local ([fe80::48f5:88b0:6093:4f67]) by ATLAS.msg.local ([fe80::48f5:88b0:6093:4f67%10]) with mapi; Sat, 24 Oct 2009 09:36:52 -0500 From: Jaime Bozza To: Jacob Myers Date: Sat, 24 Oct 2009 09:36:50 -0500 Thread-Topic: Possible scheduler (SCHED_ULE) bug? Thread-Index: AcpUKbEi7folMjnRRESecNIc+lV2JAAjKJRA Message-ID: References: <4AE2232E.10406@whotookspaz.org> In-Reply-To: <4AE2232E.10406@whotookspaz.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-stable@freebsd.org" Subject: RE: Possible scheduler (SCHED_ULE) bug? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Oct 2009 14:36:53 -0000 > > The additional information I have (over the PR) is that: > > 1) Files over 64K cause the problem, not just larger files > I thought it was over 1 MB or so. But maybe I'm wrong. ISTR that I > couldn't trigger it with some images of around 70K. I discovered it originally with a 72K file. After some tests, I found a 63= K file worked and a 65K file didn't. When I get back into the office, I ca= n test the actual boundary (65535, 65536, 65537, etc), but 64K seems pretty= logical. > > 2) switching over to SCHED_4BSD eliminates the problem - system no > longer locks. > I will have to test this. This is indeed interesting... >=20 > > 3) 7.2 amd64 doesn't have the problem - Tested a similar > configuration and was not able to duplicate on amd64 at all. > I can replicate this problem on FreeBSD 7.2/amd64 reliably. I haven't tried larger files - Maybe the boundary is different on amd64? = Doing some quick tests right now, I was able to upload a 100MB file without= a problem, but this is an AMD64 system with SMP, plus the filesystem is al= l ZFS, so there are too many things different. I'll have to setup a system= that closely mirrors the rest of my tests (UFS, ULE, no SMP, etc) before I= can say I'm not having a problem there. Jaime