A question about kernel module and system power-shutdown
Dear all,
I've just installed a Vanilla kernel (last stable version downloaded from www.kernel.org) as an exercice in order to better understand how to compile linux kernel. I loaded the .config file of the current kernel (Redhat kernel) in the menuconfig in order to restore all already activated options and I just added the support for NTFS (read and write). I proceeded all instructions as was explained in the HOWTO and apparently it works pretty well. However, there is something a bit strange. Whenever I want to shutdown the system from the command line, I run
Code:
# shutdown -h now
the option -h actually shuts down electrically the computer. Yet, by this new kernel (fortuantely I conserved the old kernel!) I have the following output:
Code:
# shutdown -h now
.
. here I see system processes and daemons being shutdown as usual
.
Turning off swap [ OK ]
Turning off quotas [ OK ]
Unmounting pipe file systems: [ OK ]
Halting system...
md: stopping all md devices.
shutdown: hda
System halted.
So as you can see at the last line we see "System halted.", but right after that, the computer halts and nothing happens, whereas I excpect it to be shutdown electrically. But this does not happen and I have to push manually the power button.
Is there a particular module that had to be activated in the new kernel that I forgot?
Thanks in advance,
Kind Regards,
Dariyoosh
---------- Post updated at 09:28 PM ---------- Previous update was at 09:27 PM ----------
Ok, finally I found the answer by myself!
I checked the config file and there were several ACPI options activated (y). Surprisingly I had ACPI=off in /boot/grub/grub.conf, I just changed it to ACPI=on and it worked pretty well.
Hi Everyone!
How can we make a socket() system call from a linux module executing in kernel space?
If any one knows, kindly tell me. It will be great.
I want to use the socket interface in linux kernel space for sending raw packets over the network.
Hamayun (0 Replies)
Hi,
We had a HP Power Trust UPS connected to our HP Server using HP Unix 11. The UPS has died, and been taken off the server. The / filesystem runs out off space (100% full) as a core file is made in /etc/opt/resmon. The core file mentions monitoring of the UPS. Removing this file, another one... (3 Replies)
Hi All,
Is there a max number of slabs that can be used per kernel module? I'm having a tough time finding out that kind of information, but the array 'node_zonelists' (mmzone.h) has a size of 5. I just want to avoid buffer overruns and other bad stuff.
Cheers,
Brendan (4 Replies)
Hi all,
I am working on USB data monitoring on Fedora Core 9. Kernel 2.6.25 has a built-in module (the one that isn't loadable, but compiles and links statically with the kernel during compilation) to snoop USB data. It is in <kernel_source_code>/drivers/usb/mon/.
I need to know if I can... (0 Replies)
Hi All,
I need to develop a kernel module which changes the IP address of a package according to its mac address. It would be a sort of L2 Nat.
Somebody know if I can do this using netfilter??
Thanks. (2 Replies)
Hi gurus
Could anybody tell me which file is read by kernel to set its default system kernal parameters values in solaris. Here I am not taking about /etc/system file which is used to load kernal modules or to change any default system kernal parameter value
Is it /dev/kmem file or something... (1 Reply)
Question may seem illogical but I still need clarification.
Can we debug kernel modules loaded on my target system using kdb / kgdb without using any other system or remote debugging?
In other words my question is can we use kdb/kgdb to debug kernel modules running on same system? (2 Replies)
Hi everyone,
I am trying to prevent the ehci_hcd kernel module to load at boot time.
Here's what I've tried so far:
1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here):
2) Blacklisted the module by adding the following string to
3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies
LEARN ABOUT FREEBSD
halt
REBOOT(8) BSD System Manager's Manual REBOOT(8)NAME
reboot, halt, fastboot, fasthalt -- stopping and restarting the system
SYNOPSIS
halt [-lnpq] [-k kernel]
reboot [-dlnpq] [-k kernel]
fasthalt [-lnpq] [-k kernel]
fastboot [-dlnpq] [-k kernel]
DESCRIPTION
The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and,
respectively, halt or restart the system. The action is logged, including entering a shutdown record into the user accounting database.
The options are as follows:
-d The system is requested to create a crash dump. This option is supported only when rebooting, and it has no effect unless a dump
device has previously been specified with dumpon(8).
-k kernel
Boot the specified kernel on the next system boot. If the kernel boots successfully, the default kernel will be booted on successive
boots, this is a one-shot option. If the boot fails, the system will continue attempting to boot kernel until the boot process is
interrupted and a valid kernel booted. This may change in the future.
-l The halt or reboot is not logged to the system log. This option is intended for applications such as shutdown(8), that call reboot
or halt and log this themselves.
-n The file system cache is not flushed. This option should probably not be used.
-p The system will turn off the power if it can. If the power down action fails, the system will halt or reboot normally, depending on
whether halt or reboot was called.
-q The system is halted or restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n
option is not specified). This option should probably not be used.
The fasthalt and fastboot utilities are nothing more than aliases for the halt and reboot utilities.
Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending
doom and cleanly terminating specific programs.
SEE ALSO getutxent(3), boot(8), dumpon(8), nextboot(8), savecore(8), shutdown(8), sync(8)HISTORY
A reboot utility appeared in Version 6 AT&T UNIX.
BSD October 11, 2010 BSD
08-25-2009
