From owner-freebsd-stable@FreeBSD.ORG Sun Nov 2 09:50:31 2008 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 0FC8E1065678 for ; Sun, 2 Nov 2008 09:50:31 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id AE34E8FC1A for ; Sun, 2 Nov 2008 09:50:30 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTP id 4C33D46B17; Sun, 2 Nov 2008 04:50:30 -0500 (EST) Date: Sun, 2 Nov 2008 09:50:30 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Ryan In-Reply-To: Message-ID: References: User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Install issues with 7.x 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: Sun, 02 Nov 2008 09:50:31 -0000 On Wed, 29 Oct 2008, Ryan wrote: > Hello, I purchased a new Clevo M860TU on the account that it ran linux very > well and was hoping it would fair the same on FreeBSD. Not so much, little > help? I posted this in mobile originally but though stable would be a better > choice. Don't know if it is more appropriate here or ACPI. > > I'm giving you as much information as I know how to get. as I cannot get > sysinstall to load I am having to type all these dmesg. The boot process is > hanging. This is all with 7.x, I can give 6.x if needed. xpt_config is the CAM configuration wait, so basically the system is waiting for a storage device to report back on whether it could be used as a root file system. I recently saw a similar report of problems involving a firewire controller on an nvidia motherboard following an upgrade to 7.x, and I wonder if you might try the following: see if 6.4 will install, and if so, install it. Then cvsup 7.x, and do a buildworld but not an installworld. This will let you build and experiment with 7.x kernels from a known-working environment. Make sure to keep a working 6.x kernel around -- I suggest something like "cp -r /boot/kernel /boot/kernel.good" before starting so you can always fall back to a good kernel. Now try building a 7.x kernel without USB or firewire support, and booting that? Also, it's worth checking there are no BIOS upgrades available for the motherboard... Robert N M Watson Computer Laboratory University of Cambridge > > Hardware: > Intel P9500 > 4gb DDR3-1066 > Nvidia 9800M GT > Atheros AR5006e > > FreeBSD 7.1-BETA2 > > These snippets of dmesg happen around the end where it hangs. > > 1. Default > > ... > cpu0: on acpi0 > ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj > 0xc6a02d40 [20070320] > ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving > operands for [OpcodeName unavailable] [20070320] > ACPI Error (psparse-0626): Method parse/execution failed > [\_PR_.CPU0._OSC] (Node 0xc68556e0), AE_AML_INTERNAL > est0: on cpu0 > p4tcc0: on cpu0 > cpu1: on acpi0 > ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj > 0xc6a0e300 [20070320] > ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving > operands for [OpcodeName unavailable] [20070320] > ACPI Error (psparse-0626): Method parse/execution failed > [\_PR_.CPU1._OSC] (Node 0xc685560), AE_AML_INTERNAL > est1: on cpu1 > p4tcc1: on cpu1 > ... > cpu0: Cx states changed > cpu1: Cx states changed > unknown: timeout waiting for read DRQ > unknown: timeout waiting for read DRQ > acd0: DVDR at ata3-master UDMA33 > GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install > run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config > > Then just stalls > > 2. No ACPI > > ... > unknown: timeout waiting for read DRQ > unknown: timeout waiting for read DRQ > acd0: DVDR at ata3-master UDMA33 > GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install > run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config > > Then just stalls > > 3. Safe Mode > > I can only tell you a little because console is spammed. It is the > same as no ACPI, but with an interrupt storm. > > ... > unknown: timeout waiting for read DRQ > unknown: timeout waiting for read DRQ > acd0: DVDR at ata3-master UDMA33 > GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install > run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config > > When it gets to the unknowns, this is spammed. > > interrupt storm detected on "irq10:"; throttling interrupt source > > Other than the interrupt storm spam, it is halted like the others. > > > 4. Single User Mode > > Same as 1, Default > > > 5. Verbose > > All I can tell you is what is spammed at the end. > > acpi: bad write to port 0x080 (32), val hex > > Where hex is ever increasing and loops when it hits 0xff01. I can also > see run_interrupt_driven_hooks message in all the spam. > > Using some googling if you add the sysctl before boot > > debug.acpi.block_bad_io=1 > > it might be of some help. This just leads to a never ending loop of > acpi errors - the scroll very fast and difficult to record might I > add! > > ... > acpi: bad write to port 0x080 (32), val hex > ACPI Exception (evregion-0529): AE_BAD_PARAMETER, Returned by handler > for [SystemIO] [20070320] > ACPI Error (psparse-0626): Method parse/execution failed [\P8XH] (Node > 0xc6850a60), AE_BAD_PARAMETER > ACPI Error (psparse-0626): Method parse/execution failed [\_GPE._L01] > [20070320] > ACPI Exception (evgpe-0687): AE_BAD_PARAMETER, while evauating GPE > method [_L01] [20070320] > --repeat-- > ... > > > FreeBSD 7.0-REL > > 7.0 is a little different than 7.1. Messages are somewhat the same but > they happen near the beginning of dmesg instead of around the end. The > run_interrupt_driven_hooks issue is nonexistant as well, but it still > hangs. I'm guessing that's a debug tool more than an error. > > 1. Default > > ... > cpu0: on acpi0 > ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj > 0xc6862580 [20070320] > ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving > operands for [OpcodeName unavailable] [20070320] > ACPI Error (psparse-0626): Method parse/execution failed > [\_PR_.CPU0._OSC] (Node 0xc682d580), AE_AML_INTERNAL > est0: on cpu0 > p4tcc0: on cpu0 > cpu1: on acpi0 > ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj > 0xc6861100 [20070320] > ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving > operands for [OpcodeName unavailable] [20070320] > ACPI Error (psparse-0626): Method parse/execution failed > [\_PR_.CPU1._OSC] (Node 0xc682d4a0), AE_AML_INTERNAL > est1: on cpu1 > p4tcc1: on cpu1 > ... > cpu0: Cx states changed > cpu1: Cx states changed > unknown: timeout waiting for read DRQ > unknown: timeout waiting for read DRQ > acd0: DVDR at ata3-master UDMA33 > GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install > > Hangs. > > 2. No ACPI > > .. > unknown: timeout waiting for read DRQ > unknown: timeout waiting for read DRQ > .. > > Hangs. > > > 3. Safe Mode > > Same interrupt storm as 7.1-BETA2. > > ... > interrupt storm detected on "irq10:"; throttling interrupt source > --repeat-- > > 4. Single User Mode > > Same as 1. Default. > > > 5. Verbose > > Hang like normal, cannot see the ACPI errors since they fly off the > scroll lock buffer. > > ... > cpu0: Cx states changed > cpu1: Cx states changed > ... > unknown: timeout waiting for read DRQ > unknown: timeout waiting for read DRQ > ... > > > Thanks again. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >