Problem with reboot on fit-pc2i

jimp

Can you try to do this:

sysctl hw.acpi.handle_reboot=1

From Diagnostics > Command or from a shell prompt.

Then try to issue a reboot from the GUI and see if it happens.

Some odd BIOS implementations require a different way of handling a reboot. If that works you can add this to /boot/loader.conf.local

hw.acpi.handle_reboot="1"

vho

Hey! Thanks for the proposal but unfortunately it still does not reboot.

Tested on 2.0-BETA5 (i386) built on Sun Jan 16 22:00:36 EST 2011

jimp

It was worth a shot I guess. You may want to change the title of the thread to mention fit pc2, there are others on the forum who have those boxes and they may have some suggestions.

My only other advice may be to try updating the BIOS or look through the BIOS for any ACPI options you might be able to flip and test.

vho

Thanks, I will continue to test and see if any bios setting to solve the problem.

jojje

Is there some trace setting which can be enabled to help capture the information you need in order to identify the cause of this problem?
I've got this hardware model too and also experience the described problem. Would be nice to have the issue not be part of the final release..

jimp

@jojje:

Is there some trace setting which can be enabled to help capture the information you need in order to identify the cause of this problem?
I've got this hardware model too and also experience the described problem. Would be nice to have the issue not be part of the final release..

Not really. The shutdown/reboot signals are typically handled via ACPI or other similar calls so it really depends a lot on the BIOS of the system involved. If it doesn't work, the only real tweak is the sysctl I mentioned earlier.

You could try a stock FreeBSD 8.1-RELEASE install and see if it can shutdown/reboot OK. I suspect it won't, but you might find more hits around the web with freebsd fit-pc reboot with more suggestions.

mark80

Nice to hear that I'm not alone on this issue.
Before I installed pfsense on this machine, I used ubuntu and had exactly the same scenario as well.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/392673

This was rectified quite quickly and after it worked a regular "reboot" just fine with Ubuntu.

I was just like you tried to change the ACPI settings of the bios, also tried updating to a newer version of bios, but it does not work in Pfsense, nor in a stock install of FreeBSD 8.1.

The machine shuts down normally when I use "shutdown-p now", it is only
rebooting that does not work. The machine hang after the normal shutdown
sequence after the message "cpu_reset: stopping Other CPUs". I have to hold
the power button for 5-6 seconds to turn it off, and then turn it on again.

The details of the hardware here:
http://www.compulab.co.il/fitpc2i/html/fitpc2i-sb-datasheet.htm

I really hope this can be corrected before pfsense 2.0 release!
Would be unfortunate to not be able to restart the server from work, without having to be present to restart it manually every time.

jimp

@mark80:

I was just like you tried to change the ACPI settings of the bios, also tried updating to a newer version of bios, but it does not work in Pfsense, nor in a stock install of FreeBSD 8.1.

If it doesn't work on FreeBSD, there may not be anything we can do about it. If you can replicate it on FreeBSD 8.1 (really you should try 8.2 also) you can open a PR with them and see if they can come up with a fix.

http://doc.pfsense.org/index.php/Policy_on_FreeBSD_issues

toomeek

@jimp:

Can you try to do this:
sysctl hw.acpi.handle_reboot=1

You just solved my issue with the latest snapshot! (2.0-RC1 (i386) built on Thu May 5 06:05:22 EDT 2011)
It hangs after message "Rebooting…" but executing this in commmand prompt solved this.
I use KVM for VM emulation.

UPDATE: uuups, seems still doesn't work :(

UPDATE2:
It doesn't work becouse adding this to (new created) file /boot/loader.conf.local doesn't work
same when I add this to /boot/loader.conf
just take a look - have to add manually (screenshot)

UPDATE3:
still hanging on "Rebooting...", even with Executed command and handle reboot enabled.

UPDATE4:
added to /etc/sysctl.conf

SOLVED: Guess what? The problem was I was using QEMU domain type instead of KVM! Checked this on different server (I'm using AMD Phenom while different server has Core i5 and has no problem). Simple change in XML of VM and problem solved.

pfSense_reboot_hang.png_thumb

pfSense_reboot.png_thumb

pfSense_loader_doesnt_work.png_thumb

mrzaz

Could jimp, mark80 and vho check with the LATEST build if it works on the fit-pc2i ?

I'm about to order the fit-pc2i but don't want to run into these issues and It would be nice to know if it works now or not.
Would be very thankful if you could test and report back.

//Dan

jimp

I do not have a fit-pc2i to test, so I can't help there. Someone else from the thread may be able to answer you.

kb0

I just received a fit-pc2i yesterday and loaded the latest nightly (june 9th). I cannot successfully reboot and setting hw.acpi.handle_reboot=1 does not resolve the problem. Would really like to get this fixed and am willing to tinker. Any suggestions?

fatsailor

Ditto here….the machines arrived today and hangs on the reboot with RC3.

The bios on my boxes (Sep 10) is not the most recent (Apr 10) which is annoying. I'll upgrade the BIOS tomorrow and retry, but I suspect no joy. At which point, I'll install 8.2 and see what I can do....but I suspect a custom kernel patch will be needed.

An interesting side note is that Linux had this same problem with the boards. Sadly, the fix was adding a command line (reboot=b) to grub.

fatsailor

I loaded up FreeBSD 8.2 Stable 201105 and it fixes the reboot problem. I'll see about putting together a custom RC3 based on 8.2 Stable.

jojje

Great leg work fatsailor !

I'll see what I can dig up from the FreeBSD mailing list and commit history, to see if there is a clean way to do a minimal patch against 8.1 (back-porting the fix).
Right I've only briefly glanced at the 8.2 change log and if I had to venture a guess, I'd say that r215513 might very well have had something to do with the the problem resolution in 8.2 .

edavid

I may add that in order to install pfsense, I had to boot the installer without ACPI (option 2 in boot menu), else it hanged during the /usr copy.
Thus I prefered not activating powerd… Better being safe on this.