From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 22 06:41:07 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 0DA5C24C for ; Mon, 22 Oct 2012 06:41:07 +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 6F17E8FC12 for ; Mon, 22 Oct 2012 06:41:06 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id b5so1834603lbd.13 for ; Sun, 21 Oct 2012 23:41:05 -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=g09V+PqkrDQjfC4jrwsPKEU4CjepnTT3xJ+xpgpVFJI=; b=gFCXOS0AKm54G0nQC5BXdMM0RsYy/yAzhWyl+98xw03s16H3xhudzkJzhI4ByEP81A nDRhBfpe0IuSUei8GDoD+239b5H5mEpMZcd8S5KWMETU/Jusyajy5fk6OLM6r96Q31VE i8kAayUIygSAPUggYAQh5OGBM1oQG4m+ypB/c= 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=g09V+PqkrDQjfC4jrwsPKEU4CjepnTT3xJ+xpgpVFJI=; b=C0j1B2MpI+U+PJss8YTVTT5gg1cjHRLZiI494d1azpBB5Hmx9+XzRpJc7eR0kAHCs5 GQzKTqiMpKyqoDAVoW3DlJ7ikTmdeZ3smvXHuvsb05+wqxtvaaOIw33pGUWCAAClJdM7 au3fhaEksmV6wbXiAZQLXgcl2dBRWSuMINpyBHEQYGnzUOmaMU5MeuPIJloWnMapD/G1 u+tTYN/zZi66+yi+Gr2X61ic1INtybM4LNYOvE0Bf2Kuatvj6lzhyEMHvKZr6mQtAg94 Bjz5He60qlqspW9yRhMZZqydA3p3Ffce8cIgG986G1j/Tqebp2p7/PhnnHbYlu5fRuw3 s9Jg== MIME-Version: 1.0 Received: by 10.112.48.10 with SMTP id h10mr3128740lbn.105.1350888065359; Sun, 21 Oct 2012 23:41:05 -0700 (PDT) Received: by 10.112.100.230 with HTTP; Sun, 21 Oct 2012 23:41:05 -0700 (PDT) In-Reply-To: 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:41:05 -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: ALoCoQmHPvUDD2xe6CN0J/7yaS8Ls2aGRlK+OjUQGjDsHm1oriyR6mTU94HqAvIwQNpx+v6kuENl 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:41:07 -0000 On Sun, Oct 21, 2012 at 11:40 PM, Peter Wemm wrote: > 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". Argh! Correctly attaches as "mfi", damn it. -- 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