Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest)
Just wanted to give everybody some closure on this issue: Through the magic of a JTAG debugger, I was able to identify that the problem was an infinite loop in the BIOS's SMI handler. I'm not sure why this didn't effect Linux -- perhaps it brought up the APs before the SMI came in. In any case, this clearly isn't a FreeBSD problem and I've punted the problem back to the BIOS vendor. Thanks to everyone who offered help and advice. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest)
Cool, glad its resolved. Jack On Fri, May 21, 2010 at 10:43 AM, Ryan Stone ryst...@gmail.com wrote: Just wanted to give everybody some closure on this issue: Through the magic of a JTAG debugger, I was able to identify that the problem was an infinite loop in the BIOS's SMI handler. I'm not sure why this didn't effect Linux -- perhaps it brought up the APs before the SMI came in. In any case, this clearly isn't a FreeBSD problem and I've punted the problem back to the BIOS vendor. Thanks to everyone who offered help and advice. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest)
I have gotten access to a system this morning, I booted and installed 8.0 RELEASE on it, it had no problems installing or afterwords booting the SMP kernel. So, is it possible there's a regression/issue in HEAD, or perhaps you have something in the PCIE expansion slots that cause it, the system I'm using has nothing. Otherwise its possible there is a hardware revision difference. Have you tried 8 REL ? I'm up and rebuilding a kernel on it right now. Jack On Tue, May 18, 2010 at 4:40 PM, Ryan Stone ryst...@gmail.com wrote: amd64 exhibits the same problem, except that it's not even polite and panics without even asking. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest)
I've also tried a 6.1-derived kernel. I doubt that it was fixed for 8.0-RELEASE and then broken again on HEAD, but I'll check and be sure. My guess is that the problem is with the BIOS. We loaned our reference board to our BIOS vendor for development purposes and the BIOS they left on it is also unable to start APs. I think that my best bet to track this down is to see how the original Intel BIOS and the bad BIOS is configuring the hardware differently. I'm not very familiar with this stuff so I'm not sure what I should be looking at. MTRRs, I guess. What else? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
HEAD can't bring up APs on Intel LC5528(Jasper Forest)
I'm trying to bring up a new board based on Intel's Jasper Forest x86 processor. I can boot a kernel without SMP without any problems, but FreeBSD is not able to start up the Application Processors if I enable SMP. The error message that I get is: AP #2 (PHY# 2) failed! panic y/n? [y] This was a i386 kernel built from HEAD as May 2nd or so. It's not always PHY#2. Some number of APs manage to start up correctly, but one usually fails. I have observed one instance where all of the APs came up properly, so it seems as though there's some kind of race that I stand a very good chance of losing at least one time in seven tries. If I disable all but one AP through device.hints I stand a pretty good chance of successfully starting that AP and booting correctly. I've been banging my head against the wall for a while now and all indications are that the AP never starts at all. I enabled the CHECK_POINTS compile-time option and and nothing ever gets written to the CMOS for the AP that fails to start. Writing to the CMOS is the second thing that the AP does after doing a cli so it's a good bet that the AP never hits that code. Linux (version 2.6.28-11) is able to boot and start the APs just fine. My suspicion is that Linux is explicitly configuring something that FreeBSD is trusting the BIOS to do. We do have the reference board around, but we're having trouble getting the original Intel BIOS programmed into it. If we can get that working again I'll let you know whether FreeBSD can boot on it. If anybody can offer any hints or ideas for debugging this it'd be greatly appreciated, as right now I'm reduced to grasping at straws. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest)
What if you use amd64, have you tried that? Low level code is different. Interesting however, maybe I can get access to one around here, will see. Jack On Tue, May 18, 2010 at 2:32 PM, Ryan Stone ryst...@gmail.com wrote: I'm trying to bring up a new board based on Intel's Jasper Forest x86 processor. I can boot a kernel without SMP without any problems, but FreeBSD is not able to start up the Application Processors if I enable SMP. The error message that I get is: AP #2 (PHY# 2) failed! panic y/n? [y] This was a i386 kernel built from HEAD as May 2nd or so. It's not always PHY#2. Some number of APs manage to start up correctly, but one usually fails. I have observed one instance where all of the APs came up properly, so it seems as though there's some kind of race that I stand a very good chance of losing at least one time in seven tries. If I disable all but one AP through device.hints I stand a pretty good chance of successfully starting that AP and booting correctly. I've been banging my head against the wall for a while now and all indications are that the AP never starts at all. I enabled the CHECK_POINTS compile-time option and and nothing ever gets written to the CMOS for the AP that fails to start. Writing to the CMOS is the second thing that the AP does after doing a cli so it's a good bet that the AP never hits that code. Linux (version 2.6.28-11) is able to boot and start the APs just fine. My suspicion is that Linux is explicitly configuring something that FreeBSD is trusting the BIOS to do. We do have the reference board around, but we're having trouble getting the original Intel BIOS programmed into it. If we can get that working again I'll let you know whether FreeBSD can boot on it. If anybody can offer any hints or ideas for debugging this it'd be greatly appreciated, as right now I'm reduced to grasping at straws. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest)
amd64 exhibits the same problem, except that it's not even polite and panics without even asking. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest)
LOL, ok, I'm beating the bushes here Ryan, and I think I can get a system although it may be a day or two. Will let you know. Jack On Tue, May 18, 2010 at 4:40 PM, Ryan Stone ryst...@gmail.com wrote: amd64 exhibits the same problem, except that it's not even polite and panics without even asking. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest)
On Tue, 18 May 2010 19:40:13 -0400 Ryan Stone ryst...@gmail.com wrote: amd64 exhibits the same problem, except that it's not even polite and panics without even asking. Could you please try disabling legacy USB device support in BIOS if such an option is provided in your BIOS setup and see if that changes anything? -- Alexander Kabaev signature.asc Description: PGP signature
