From owner-freebsd-current@FreeBSD.ORG Fri Dec 5 08:29:04 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE33A1065670 for ; Fri, 5 Dec 2008 08:29:04 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from po-out-1718.google.com (po-out-1718.google.com [72.14.252.152]) by mx1.freebsd.org (Postfix) with ESMTP id 8A21B8FC21 for ; Fri, 5 Dec 2008 08:29:04 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by po-out-1718.google.com with SMTP id y22so6865273pof.3 for ; Fri, 05 Dec 2008 00:29:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=8Ms8/lVpD05LyJOjCaxn83JgSr1bqJLSz4Nvl1gJHbU=; b=UKFLtaOIDCj4suqecbstzy9GlPuHuENhyYnf3pbXUV1/zl/pg1FguZrp+R0dL4P0Bx 1Qx6Xw6DV0MJ+DTEHNC60JvrZw7Z1yzZxckMbHqz0Q1ep9jJAgAjUkF2iD0f1mKypocm m5BrVJIKcgPHlwUiTAhoFbQ3TMrXNl9w81pmk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=gPPEvEBFSjWP+ddJQRmla469jpOxYYjxD8qVBks+nbFCq2NijBugoCwkqN+Wkkolw7 G9tW0fHzmxsLSdHCvPif26XO6UUL8BC+NSl6/kX0ts/25ZRo6MM1aPkIW9o6MP6BIdgI AxxJ+H8KsIWrzokp7qOWLZM1O4+Oan5WTO8WQ= Received: by 10.141.171.3 with SMTP id y3mr794285rvo.263.1228465743732; Fri, 05 Dec 2008 00:29:03 -0800 (PST) Received: by 10.140.158.13 with HTTP; Fri, 5 Dec 2008 00:29:03 -0800 (PST) Message-ID: <7d6fde3d0812050029r7308ec57jaed2733a2396a9fe@mail.gmail.com> Date: Fri, 5 Dec 2008 00:29:03 -0800 From: "Garrett Cooper" To: "Chris Ruiz" In-Reply-To: <58c737d70812041934v359e9833vbe68e6be871875f8@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <49226603.5030204@nixil.net> <200812041421.53099.jhb@freebsd.org> <58c737d70812041934v359e9833vbe68e6be871875f8@mail.gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: lockup booting 8.0-CURRENT-200811 snap image X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Dec 2008 08:29:04 -0000 On Thu, Dec 4, 2008 at 7:34 PM, Chris Ruiz wrote: > On Thu, Dec 4, 2008 at 1:21 PM, John Baldwin wrote: >> On Tuesday 18 November 2008 01:51:47 am Phil Oleson wrote: >>> Hi, I've been trying to update my system to Current to try out the new >>> usb stack etc.. >>> and have had some problems. Initially I attempted to just do a cvsup, >>> make buildworld, >>> make kernel and had problems at the reboot. Ended up having to use the >>> livecd to swap >>> out the kernel (loader was strangely hanging before I could type unload; >>> boot kernel.old) >>> >>> Anyways, I picked up a new drive to split my system up to have a >>> working 7 & current. >>> So, I downloaded the 200811 snap iso's for amd64 & i386 and tried to >>> boot to them. >>> Same/similar lockup happens.. now since this board currently doesn't >>> have a serial port >>> I've had to handtype what was left on the screen.. so hopefully it's >>> enough for now. >>> >>> System: INTEL BLKDG35EC 775 G35 (flashed to the **ECG3510M.86A.0107** >>> Bios Image) >>> INTEL C2Q Q9300 2.5G 775 >>> 2 gigs memory (messed up on original order and havnt fixed >>> it yet) >>> using the built-in Intel video.. >>> >>> so the i386 and the amd64 dvd image I booted with had the same stopping >>> screen/output >>> that I could see.. this is what I was able to get down from a verbose boot. >>> >>> ------------------------------------------------------ >>> Initial Probe 0 10 N 0 3 4 5 7 9 10 11 12 >>> Validation 0 10 N 0 3 4 5 7 9 10 11 12 >>> After Disable 0 255 N 0 3 4 5 7 9 10 11 12 >>> acpi_hpet0: iomem 0xfed00000-0xfed003ff on >>> acpi0 >>> acpi_hpet0: vend: 0x8086 rev: 0x1 num: 2 hz: 14318180 opts: legacy_route >>> 64-bit Timecounter "HPET" frequency 143181800 Hz quality 900 >>> acpi_button0: on acpi0 >>> pcib0: port 0xcf8-0xcff on acpi0 >>> pci0: on pcib0 >>> pci0: domain=0, physical bus=0 >>> found-> vendor=0x8086, dev=0x2980, revid=0x03 >>> domain=0, bus=0, slot=0, func=0 >>> class=06-00-00, hdrtype=0x00, mfdev=0 >>> cmdreg=0x0006, statreg=0x2090, cachelnsz=0 (dwords) >>> lattimer=0x00 (0 ns), mingnt=0x00 (0ns), maxlat=0x00 (0 ns) >>> found-> vendor=0x8086, dev=0x2982, revid=0x03 >>> domain=0, bus=0, slot=2, func=0 >>> class=03-00-00, hdrtype=0x00, mfdev=1 >>> cmdreg=0x0007, statreg=0x0090, cachelnsz=0 (dwords) >>> lattimer=0x00 (0 ns), mingnt=0x00 (0ns), maxlat=0x00 (0 ns) >>> intpin=a, irq=11 >>> powerspec 2 supports D0 D3 current D0 >>> MSI supports 1 message >>> map[10]: type Memory, range32, base 0x90200000, size 20, >>> enabled >>> -------------------------------- >>> >>> >>> Any suggestions on how to proceed? >>> >>> I'll see about installing the new install on the new drive starting at >>> RELENG_7 >>> and updating to HEAD from there.. so any source changes will have to wait on >>> completing that.. but anything would help. >> >> Try setting hw.pci.mcfg=0 > > I also have an Intel board (INTEL DQ35JO) and had posted last month > with a boot hang in the same place. I recieved a quick reply from > the list and setting hw.pci.mcg=0 fixed everything. > > Should this be marked as a known problem somewhere on the wiki? It > appears to happen to Intel boards with onboard graphics and I imagine > that as more people migrate from 7.x to CURRENT that this will happen > to more users. > > Thanks, > > Chris Ruiz > >> >> -- >> John Baldwin This definitely should be listed in a FAQ, IMHO. Where would the best place be for this? -Garrett