From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 22 06:40:13 2012 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 456521F7 for ; Mon, 22 Oct 2012 06:40:13 +0000 (UTC) (envelope-from peter@wemm.org) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id AE0238FC08 for ; Mon, 22 Oct 2012 06:40:12 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id b5so1834155lbd.13 for ; Sun, 21 Oct 2012 23:40:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wemm.org; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xZL5CGO+tymt75CMtLoXcJPqVaVYJVYl7zF71nLkuEM=; b=0SNuP1VyGz5o/HhcR7sAjXh8n78vVEFA8LkidoTmJowhwGCNokTzC/TH0ogiBieQnK /69GjG0DlndgjNk++Q8xednJdh2zIN9XPXexljzj1g0ap3XeOnkjb55oZr/51Lg0LcSO /Cg94VQXOhgalpNVS70bhBRETakCI9cMmaW/A= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=xZL5CGO+tymt75CMtLoXcJPqVaVYJVYl7zF71nLkuEM=; b=SM8HVFUduktq/h8LmF1nOAQ5DmDI9qafmjMtYKtKbRzGrGWkFZ2hHUqvH4h5XY4S7p 9Eju5rE7+Yqw+ikeOQdPSLqKx+4CZK/koR4u/MwNN94o9dWU9wM2AzXsDM2mfX3ZpZ4S KdDua1S6yXVecRiQ4cyVD+wubhgEBNz9ozCe6J+ghaXTB+9djfrvOpzqfw/2TY3jm3Xk x+IEGYMmb1PbZ1KBuni9ksiyQgzSWB20bhDhcFdQCNt38n6kfeyibk9NN1hiYaGqWzhL hFvf+wH+F5C5qzao6AeNc/gQUruElu/2gQNK5jucTHsk2cB4ApKzaalCcc99lTzNcr3n fuoA== MIME-Version: 1.0 Received: by 10.112.48.10 with SMTP id h10mr3128058lbn.105.1350888011402; Sun, 21 Oct 2012 23:40:11 -0700 (PDT) Received: by 10.112.100.230 with HTTP; Sun, 21 Oct 2012 23:40:11 -0700 (PDT) In-Reply-To: <201208281238.48041.jhb@freebsd.org> References: <20120827203817.GB44988@mikea.ath.cx> <201208280934.14161.jhb@freebsd.org> <20120828140507.GB64344@mikea.ath.cx> <201208281238.48041.jhb@freebsd.org> Date: Sun, 21 Oct 2012 23:40:11 -0700 Message-ID: Subject: Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI From: Peter Wemm To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQll3kyp8hdC4g6AC9nHLGhdLj/HXGREe0pDtWvDfkkBbMOJCwKw7hT6z8ptmWF6Ngaen18e Cc: freebsd-amd64@freebsd.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 06:40:13 -0000 On Tue, Aug 28, 2012 at 9:38 AM, John Baldwin wrote: > On Tuesday, August 28, 2012 10:05:07 am Mike A wrote: >> On Tue, Aug 28, 2012 at 09:34:14AM -0400, John Baldwin wrote: >> > 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? >> >> Thanks VERY MUCH (and come collect your steak dinner at Cattlemen's Cafe in >> OKC, next time you're in the area) for the very quick response. >> >> I will be happy to try that, but need guidance. This is an install from >> CD (burned from FreeBSD-9.1-RC1-amd64-disc1.iso), and I don't know how to >> insert a loader hint in that process. > > When the loader menu pops up, choose the "escape to loader prompt" option, > then type 'set hint.mpt.0.msi_enable=0' followed by 'boot'. There's no > guarantee this will help, btw, just something to try out first. > > If that doesn't work, you can also try setting 'machdep.kdb_on_nmi=0' using > the same trick. > > If that still doesn't help, please boot another OS that does and get the > output of 'lspci -v' or 'pciconf -lvb' or equivalent so we can see exactly > which mpt adapter it is. I think there is one class of mpt(4) cards that > we do not yet support properly. Ah, yes, this PR: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=149220 > > I think this may in fact be your adapter. This was fixed after 9.0, so try > a 9.1-RC1 install disk instead and see if it works better. Is it actually an mpt? There's a number of current servers that have *mfi* raid controllers that are mis-identified as mpt and being claimed by the mpt driver. Naturally this does not work well. I recognize the exact failure text from a failure we had in the freebsd.org cluster a few days ago with 9.0-RELEASE. The good news is that 9-STABLE or 9.1-RC get it right, at least on our hardware. It correctly attaches as "mpt". The bad news is that *our* particular servers have newer broadcom chips in them and none of the 9.x releases or 9.1-RC's work on it, at all. That's probably not relevant to the original reporter though. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell