From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 28 13:54:05 2012 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07B811065676 for ; Tue, 28 Aug 2012 13:54:05 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id D19948FC12 for ; Tue, 28 Aug 2012 13:54:04 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 28872B94F; Tue, 28 Aug 2012 09:54:04 -0400 (EDT) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Tue, 28 Aug 2012 09:34:14 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <20120827203817.GB44988@mikea.ath.cx> In-Reply-To: <20120827203817.GB44988@mikea.ath.cx> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201208280934.14161.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 28 Aug 2012 09:54:04 -0400 (EDT) Cc: Subject: Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Aug 2012 13:54:05 -0000 On Monday, August 27, 2012 4:38:17 pm Mike A wrote: > IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e) > > I just got handed 4 of the subject boxes with instructions "put 'em to > work". Naturally I tried FreeBSD first, on one of the machines. Boot from > the 9.0 AMD64 boot-only install CD fails. Things look fine until the last > several lines of the (verbose enabled) boot sequence, which (from an > insufficiently-wide phone camera capture) are: > > " > mpt0: port 0x3000-0x[lost off right edge of phone] > xc5d00000-0xc5deffff irq 34 at device 0.0 on pci[lost] > mpt0: attempting to allocate 1 MSI vectors (1 su[lost] > msi: routing MSI IRQ 256 to local APIC 0 vector [lost] > mpt0: using IRQ 256 for MSI > mpt0: soft reset failed, device not running > NMI ISA 2c, EISA 0 > NMI ... going to debugger > mpt0: hard reset failed > " Does setting 'hint.mpt.0.msi_enable=0' in the loader make a difference? -- John Baldwin