Date: Fri, 14 Sep 2012 11:46:03 -0500 From: Mike A <mikea@mikea.ath.cx> To: freebsd-scsi@freebsd.org Subject: Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI Message-ID: <20120914164603.GA34637@mikea.ath.cx> In-Reply-To: <201208290818.20990.jhb@freebsd.org> References: <20120827203817.GB44988@mikea.ath.cx> <201208281238.48041.jhb@freebsd.org> <20120828210618.GD69985@mikea.ath.cx> <201208290818.20990.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 29, 2012 at 08:18:20AM -0400, John Baldwin wrote: > Humm, that is bizarre. All the early bootstrap code just relies on the BIOS > to perform disk I/O, etc. Can you PXE boot these machines? That might be a > way to get the CD out of the picture. I haven't seen any machines with your > symptoms. At the least, if a machine does have a problem with the boot process > due to a bug or some such, it is consistent in having the problem every time, > not suddenly failing after working. > > Also, to be honest, the original NMI in itself is a bit odd. If you are having > these problems now I do wonder if there isn't an underlying hardware issue. > Regardless, I think netbooting would be a good thing to look to get the CD/DVD > bit out of the way. All the stars finally moved to the right places, and I was able to try booting from a 9.1 amd64 memstick made from FreeBSD-9.1-RC1-amd64-memstick.img. That failed, both without and with boot loader hints. I had a movie camera running to catch the console message traffic. The last normal messages on the screen have to do with device mfi0. Here is the last screenfull: class=01-04-00, hdrtype=0x00, mfdev=0 cmdreg=0x0047, statreg=0x0010, cachelnsz=16 (dwords) lattimer==0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=7 powerspec 3 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit MSI-X supports 16 messages in map 0x14 map[10]: type I/O Port, range 32, base 0x3000, size 8, enabled pcib3: allocated I/O port range (0x3000-0x30ff) for rid 10 of pci0:22:0:0 map[14]: type Memory, range 64, base 0xc5d40000, size 14, enabled pcib3: allocated memory range (0xc5d40000-0xcd43fff) for rid 14 of pci0:22:0:0 map[1c]: type Memory, range 64, base 0xc5d00000, size 18, enabled pcib3: allocated memory range (0xc5d00000-0xc5d3ffff) for rid 1c of pci0:22:0:0 pcib3: matched entry for 22.0.INTA pcib3: slot 0 INTA hardwired to IRQ 34 mfi0: <Thunderbolt> port 0x3000-0x30ff mem 0xc5d40000-0xcfd43fff,0xc5d00000-0xc5 d3ffff irq 34 at device 0.0 on pci22 mfi0: attempting to allocate 1 MSI vectors (1 supported) msi: routing MSI IRQ 264 to local APIC 0 vector 59 mfi0: using IRQ 264 for MSI mfi0: Using MSI mfi0: Megaraid SAS driver Ver 4.23 mfi0: MaxCmd = 3f0 MaxSgl = 46 state=b75003f0 mfi0: Max fw cmds= 1000, sizing driver pool to 128 After this, the screen goes blank, then to "system initializing" on the very bottom line, which indicates that the system has been reset. The previous screen updates so quickly that lines are overlaid on the video from my camera. I think I can get a high-speed camera; the training video people are next door. I can download and boot a Linux system to get the PCI information for you, if that will get us any farther forward, but that will require more time. Please advise. Thanks again for the help so far. I *will* get this critter going. -- Mike Andrews, W5EGO mikea@mikea.ath.cx Tired old sysadmin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120914164603.GA34637>