From owner-freebsd-current@FreeBSD.ORG Fri Jul 9 18:12:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52D9916A4CE for ; Fri, 9 Jul 2004 18:12:47 +0000 (GMT) Received: from smtp003.bizmail.yahoo.com (smtp003.bizmail.yahoo.com [216.136.130.195]) by mx1.FreeBSD.org (Postfix) with SMTP id 3C99543D2F for ; Fri, 9 Jul 2004 18:12:47 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: from unknown (HELO optimator.noacks.org) (noackjr@supercrime.org@70.240.179.20 with login) by smtp003.bizmail.yahoo.com with SMTP; 9 Jul 2004 18:12:46 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 4E22A618F; Fri, 9 Jul 2004 13:12:46 -0500 (CDT) Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 03830-02-2; Fri, 9 Jul 2004 13:12:45 -0500 (CDT) Received: from compgeek.noacks.org (compgeek [192.168.1.10]) by optimator.noacks.org (Postfix) with ESMTP id 22A126157; Fri, 9 Jul 2004 13:12:45 -0500 (CDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by compgeek.noacks.org (8.12.11/8.12.11) with ESMTP id i69ICi4o059127; Fri, 9 Jul 2004 13:12:44 -0500 (CDT) (envelope-from noackjr@alumni.rice.edu) Message-ID: <40EEE01C.6090400@alumni.rice.edu> Date: Fri, 09 Jul 2004 13:12:44 -0500 From: Jon Noack User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040629) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steve Kargl References: <20040705184940.GA2651@tybalt.greiner.local> <200407081317.53981.jhb@FreeBSD.org> <20040709111955.2901ce5b.taku@tackymt.homeip.net> <200407091315.16899.jhb@FreeBSD.org> <40EED38D.9010903@alumni.rice.edu> <20040709172511.GA10540@troutmask.apl.washington.edu> <40EEDBB1.6090903@alumni.rice.edu> <20040709180635.GA11419@troutmask.apl.washington.edu> In-Reply-To: <20040709180635.GA11419@troutmask.apl.washington.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at noacks.org cc: Taku YAMAMOTO cc: freebsd-current@freebsd.org Subject: Re: Native preemption is the culprit [was Re: today's CURRENT lockups] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jul 2004 18:12:47 -0000 On 07/09/04 13:06, Steve Kargl wrote: > On Fri, Jul 09, 2004 at 12:53:53PM -0500, Jon Noack wrote: >> On 07/09/04 12:25, Steve Kargl wrote: >>> On Fri, Jul 09, 2004 at 12:19:09PM -0500, Jon Noack wrote: >>>> On 07/09/04 12:15, John Baldwin wrote: >>>>> My test machine is not a true SMP machine either, just HTT. >>>>> It has been running a -j 256 worldloop overnight with no >>>>> problems, so I committed a slightly modified version of the >>>>> patch yesterday. >>>> >>>> Did you test with a UP kernel? After your latest commit I have >>>> been experiencing regular hard locks on my pre-HTT P4 machine. >>>> Backing out rev. 1.114 of sched_ule.c fixes it. See my >>>> previous message (Re: FreeBSD keeps hanging......): >>>> http://docs.freebsd.org/cgi/mid.cgi?40EECC49.3070501 >>> >>> I've tested it on a UP kernel (HTT enabled, ACPI disabled, APIC >>> enabled, ULE). Appears to work fine. >> >> Perhaps it's just extraneous information, but if it's really a UP >> kernel (as in, no 'options SMP') then whether you have HTT enabled >> doesn't matter at all -- the kernel won't use it. > > Yes, I know. :-) I'm just reporting what dmesg tells me about the > CPU. > > CPU: Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz (1994.12-MHz > 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 > Features=0xbfebf9ff Mine also lists HTT, but doesn't actually support it: CPU: Intel(R) Pentium(R) 4 CPU 2.53GHz (2539.10-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febfbff I remember a discussion about this a long time ago, but don't remember the details. Regardless, the flag doesn't actually mean the processor supports HTT. Jon