From owner-freebsd-current@FreeBSD.ORG Fri Sep 24 23:29:42 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 104A016A502 for ; Fri, 24 Sep 2004 23:29:42 +0000 (GMT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id D73BD43D53 for ; Fri, 24 Sep 2004 23:29:41 +0000 (GMT) (envelope-from adamk@voicenet.com) Received: from [192.168.0.201] (pcp04364354pcs.glstrt01.nj.comcast.net[68.44.156.246]) by comcast.net (rwcrmhc11) with ESMTP id <2004092423294101300ls94ne> (Authid: akirchhoff135014); Fri, 24 Sep 2004 23:29:41 +0000 Message-ID: <4154ADE7.1030607@voicenet.com> Date: Fri, 24 Sep 2004 19:29:43 -0400 From: Adam K Kirchhoff User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 5.3-RELEASE TODO X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2004 23:29:42 -0000 Scott Long wrote: >On Fri, 24 Sep 2004, Adam K Kirchhoff wrote: > > >>David Syphers wrote: >> >> >> >>>On Friday 24 September 2004 01:43 am, Oliver Brandmueller wrote: >>> >>> >>> >>> >>>>On Fri, Sep 24, 2004 at 01:41:22AM -0600, Scott Long wrote: >>>> >>>> >>>> >>>> >>>>>This is a list of open issues that need to be resolved for FreeBSD 5.3. >>>>>If you have any updates for this list, please e-mail re@FreeBSD.org. >>>>> >>>>>Show stopper defects for 5.3-RELEASE >>>>> >>>>> >>>>> >>>>> >>>>There seems to be an issue with SMP and ACPI which came into the tree >>>>somewhere after BETA3, see the corresponding threads in current@ >>>> >>>>SMP problems with -CURRENT? (and BETA5) >>>> >>>> >>>> >>>> >>>This thread mentions APIC several times (one person saying the problems went >>>away when a kernel "without device apic" was made, and someone else saying, >>>"clearly there was a bug introduced in the ACPI or APIC code"). >>> >>> >>> >>> >>That would be me. Here's a summary of what I encountered (all this can >>be found in the "SMP problems with -CURRENT (and BETA5)": >> >>With HTT enabled in the BIOS: >> >>1) With ACPI and APIC enabled: Locking up after detecting my hard drives >>and launching the second processor. >> >>2) With ACPI disabled and APIC enabled: Crashing with a "Fatal trap 9". >> >>3) With both ACPI and APIC disabled: Success. >> >>With HTT disabled in the BIOS: >> >>1) With ACPI and APIC enabled: Locking up after detecting my hard drives. >> >>And, I'd agree with your assesment that, no matter the cause, this is a >>pretty significant show-stopping bug :-) >> >>Adam >> >> >> >> > >Agreed. John and Nate, can you two please look into this and report back? >Also, Adam, would it be possible for you to step through the RELENG_5 >commits and find the point where the problem occurs? > > > I can tell you right now that it's definitely between BETA4 and BETA5... I probably won't have much time to through the various commits for a little over a week, though. Once I'm back, though, I'll gladly give it a shot if no one beats me to it. Adam