Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI
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] xc5d0-0xc5de 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 " after which the firmware reinitializes the system and the sequence starts over, totally repeatable. The IBM literature says the RAID adapter is an IBM ServeRaid M5110e, the RAID configuration firmware calls it a MegaRaid, and FreeBSD identifies it as an LSILogic SAS/SATA Adapter. I don't know what it really is, but it's getting in the way. I'd really like to add these to the stable, and particularly want to run them in 64-bit mode; 32-bit just isn't roomy enough. This isn't my first rodeo. If this is an appropriate venue, then what do you need from me? Or have I just got incompatible, unsupported hardware? If it's not, then a flameless) pointer to the appropriate venue will be greatly appreciated. Many thanks, from -- Mike Andrews, W5EGO mi...@mikea.ath.cx Tired old sysadmin ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI
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] > xc5d0-0xc5de 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 ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI
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] > > xc5d0-0xc5de 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. -- Mike Andrews, W5EGO mi...@mikea.ath.cx Tired old sysadmin ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI
Hello Mike On 28.08.2012 16:05, Mike A wrote: On Tue, Aug 28, 2012 at 09:34:14AM -0400, John Baldwin wrote: Does setting 'hint.mpt.0.msi_enable=0' in the loader make a difference? 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. On the installed system create, or edit, the file /boot/loader.conf and add the line like this: hint.mpt.0.msi_enable="0" Then you need to reboot to test. bye Fabian ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI
On Tue, Aug 28, 2012 at 04:41:54PM +0200, Fabian Wenk wrote: > Hello Mike > > On 28.08.2012 16:05, Mike A wrote: > > On Tue, Aug 28, 2012 at 09:34:14AM -0400, John Baldwin wrote: > >> > >> Does setting 'hint.mpt.0.msi_enable=0' in the loader make a difference? > > > 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. > > On the installed system create, or edit, the file > /boot/loader.conf and add the line like this: > > hint.mpt.0.msi_enable="0" > > Then you need to reboot to test. I would happily do precisely that, if only I could get the system to install. The failure occurs during boot of the install CDROM, before bsdinstall ever gets started. I suspect that I need to do something like the following: Read in the entire boot CDROM to a directory tree using rsync or equivalent; Edit the boot loader hints file to add that hint; Make an ISO out of the directory tree; Burn it to CDROM; and Try again. If this is flawed, please say where and how. Thanks! -- Mike Andrews, W5EGO mi...@mikea.ath.cx Tired old sysadmin ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI
On Tue, Aug 28, 2012 at 09:50:15AM -0500, Mike A wrote: > On Tue, Aug 28, 2012 at 04:41:54PM +0200, Fabian Wenk wrote: > > Hello Mike > > > > On 28.08.2012 16:05, Mike A wrote: > > > On Tue, Aug 28, 2012 at 09:34:14AM -0400, John Baldwin wrote: > > >> > > >> Does setting 'hint.mpt.0.msi_enable=0' in the loader make a difference? > > > > > 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. > > > > On the installed system create, or edit, the file > > /boot/loader.conf and add the line like this: > > > > hint.mpt.0.msi_enable="0" > > > > Then you need to reboot to test. > > I would happily do precisely that, if only I could get the system to > install. The failure occurs during boot of the install CDROM, before > bsdinstall ever gets started. > > I suspect that I need to do something like the following: > > Read in the entire boot CDROM to a directory tree using rsync or > equivalent; > > Edit the boot loader hints file to add that hint; > > Make an ISO out of the directory tree; > > Burn it to CDROM; and > > Try again. > > If this is flawed, please say where and how. Thanks! When you boot from the CD you should get to a menu and option 2 is escape to the loader prompt. If you use that to get the prompt you should be able to do set hint.mpt.0.msi_enable="0" to set the hint manually then do boot to continue the boot process Regards, Gary ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI
Hello Mike On 28.08.2012 16:50, Mike A wrote: On Tue, Aug 28, 2012 at 04:41:54PM +0200, Fabian Wenk wrote: On the installed system create, or edit, the file /boot/loader.conf and add the line like this: hint.mpt.0.msi_enable="0" Then you need to reboot to test. I would happily do precisely that, if only I could get the system to install. The failure occurs during boot of the install CDROM, before bsdinstall ever gets started. OK, I did had to wade through the only documentation too, as I did not see an installer recently. ;) During the FreeBSD boot menu (with the several options to choose), use "2. Escape to loader prompt". There you need to type the following lines: set hint.mpt.0.msi_enable="0" boot Hopefully this should do the trick, but this needs to be done again after the system is installed, until you have set the option in the /boot/loader.conf. bye Fabian ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI
On Tue, Aug 28, 2012 at 05:31:20PM +0200, Fabian Wenk wrote: > Hello Mike > > On 28.08.2012 16:50, Mike A wrote: > > On Tue, Aug 28, 2012 at 04:41:54PM +0200, Fabian Wenk wrote: > >> On the installed system create, or edit, the file > >> /boot/loader.conf and add the line like this: > >> > >> hint.mpt.0.msi_enable="0" > >> > >> Then you need to reboot to test. > > > > I would happily do precisely that, if only I could get the system to > > install. The failure occurs during boot of the install CDROM, before > > bsdinstall ever gets started. > > OK, I did had to wade through the only documentation too, as I > did not see an installer recently. ;) > > During the FreeBSD boot menu (with the several options to > choose), use "2. Escape to loader prompt". There you need to type > the following lines: > > set hint.mpt.0.msi_enable="0" > boot > > Hopefully this should do the trick, but this needs to be done > again after the system is installed, until you have set the > option in the /boot/loader.conf. Very much obliged to you, Mike Meyer, and Gary Palmer. I will go up and lay hands on the hardware in a bit. -- Mike Andrews, W5EGO mi...@mikea.ath.cx Tired old sysadmin ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI
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] > > > xc5d0-0xc5de 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. -- John Baldwin ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI
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] >> > > xc5d0-0xc5de 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 - pe...@wemm.org; pe...@freebsd.org; pe...@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 ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI
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] >>> > > xc5d0-0xc5de 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 - pe...@wemm.org; pe...@freebsd.org; pe...@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 ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"