Tag Info

Hot answers tagged

3

AFAIK a reset button just shorts out 2 pins on the board to kill the power, then when it's reset it's like you've switched it off and on again. Effectively all it does.


3

Probably not the answer but a contribution. Found the same error in a couple of virtual servers, after an uptime alarm, and could see all services being stopped nicely and found that 109 was an entry after a planned reboot from Citrix service event ID 1074 Log Name: System Source: USER32 Event ID: 1074 Task Category: None Level: ...


3

Yes. The virsh shutdown command (or other implementations of "shutdown" using libvirt, as in virt-manager) instructs the guest OS to shut down cleanly. From the man page: shutdown domain-id Gracefully shuts down a domain. This coordinates with the domain OS to perform graceful shutdown, so there is no guarantee that it will succeed, and may ...


2

It's a crapshoot. There's a certain amount of spin-up/spin-down latency associated with changing the CPU frequency, and this can negatively affect certain workloads (typically ones that are CPU-hungry but still memory-bound, resulting in uneven but high-throughput CPU access patterns). Modern CPUs seem to perform much better with this than even just two ...


2

Usually this is due to automatic updates. Both the 109 and 13 Event IDs can indicate a reboot. Look for update messages in the event log from WindowsUpdateClient, for example: ... Also, if someone pressed the power button that can initiate a graceful shutdown with many systems.


2

I did dmesg|grep acpi and found that acpi was set to acpi=off in grub.conf, which I set it to acpi=on It worked !


2

Check your bios settings - is there a 'speedstep' setting that is disabled? If so, enable it. Maybe the setting has another name? It's probably under the power saving bios settings somewhere. Run dmesg right after trying to modprobe the module and see if any useful information is output there. Try running modprobe -v acpi-cpufreq, although I doubt that ...


2

Thanks for all those who helped. :) I tried passing "reboot=bios" as kernel option. This solved the reboot hanging problem. My system is no more hanging now. Read this for details on passing kernel options and seeing alternative values that may solve your problem. For some systems, such as the Dell T1600, reboot and acpi kernel options may not be ...


1

If it is a server, then which services needs to be up? If you serve HTTP only and need SSH also, just monitor HTTP, HTTPS and SSH traffic and if it is idle for more than X minutes hibernate it. You can use tshark to check this.


1

power_button is a script, so all you need is to save executing backtrace from that script. The idea is to write a script that analyzes processes tree from launched power_button upwards and the caller process should be somewhere within. See this answer. Put the script into /usr/lib/acpid/power_button and save its output to a file: that should identify the ...


1

Start with the output of dmidecode -t 1, and use that to help differentiate between systems. [root@LAS ~]# dmidecode -t 1 # dmidecode 2.11 SMBIOS 2.7 present. Handle 0x0100, DMI type 1, 27 bytes System Information Manufacturer: HP Product Name: ProLiant DL380 G6 Version: Not Specified Serial Number: 2UX95306KT ...


1

From Task Manager, select View... CPU History... One Graph Per CPU.


1

You can shut your freenas down by executing a plink.exe command. (Google "plink" to find the download area.) If you can enable ssh access to your freenas, you can execute plink -ssh -pw [PASSWORD] [root]@[IP OF FREENAS] shutdown -p now where PASSWORD is the password of the freenas root user and IP OF FREENAS is the IP address of your freenas. To wake up ...


1

There is no way to get FreeNAS to do a suspend, because AFAIK they didn't compile the necessary ACPI stuff into the system. Actually I think I've been wrong here! I just found acpi feature request and trac commit log. It sounds a little vague though, so you may want to ask at FreeNAS Dev Mailing list


1

Have you considered the possibility of someone simply hitting the power button ? That will cause exactly the behavior you described.


1

We've got a same problem here. Hope our steps help to solve similar problems. We have a hyper-v stand-alone with 2x Server 2008 R2 as VM installed. By searching the internet we found some hands-on: Windows activation key (if it's expired, it could be give such a problems.. don't ask me why...) Outdated drivers Shutdown - HyperV - energy problems What ...


1

http://www.novell.com/documentation/suse91/suselinux-adminguide/html/ch09s03.html has a section that says: Some newer machines (especially SMP systems and AMD64 systems) need ACPI for configuring the hardware correctly. On these machines, disabling ACPI can cause problems. I don't know if it's still relevant. I didn't find anything similar on Red ...


1

for debian squeeze amd64 on Dell latidute 390MT, with sandy bridge use reboot=pci in details : $>sudo nano /etc/default/grub change the : GRUB_CMDLINE_LINUX_DEFAULT="quiet" to : GRUB_CMDLINE_LINUX_DEFAULT="reboot=pci quiet" (cltr+0, cltr+x) $>sudo update-grub reboot now works perfect/



Only top voted, non community-wiki answers of a minimum length are eligible