How to know if IRQ full or blocked?
 

Hi guys,

is there any command or something to survey whether IRQ in system is full?

I've got a small Linux box (none distribution).
A micro controller reacts to it when I push a button B, but Kernel doesn't seem to receive the interrupt.
In case I push the other button A, receives the interrupt well.
So I thought IRQ full in system.
or something may be blocking its interrupt.

Also if IRQ full or blocked, can I edit it to receive the interrupt from the button B?
Please let me know it if possible.

Any advice?

Thanks in advance.

cat /proc/interrupts list should be small so post the output pls

Thanks a lot aus9,

Here's the output :

~# cat /proc/interrupts
CPU0
0: 7552517 Mv Timer Tick
3: 3221 serial
12: 0 ehci_hcd:usb2
17: 0 ehci_hcd:usb1
21: 427927 eth0
28: 0 cesa
29: 10428 mvSata
34: 1 MiCon
Err: 0

well I am looking but can not see a conflict.

can you expand on your no distro pls?

2) are you wanting to map keyboard press button a to b when allegedly button a already works?

3) do not post full logs but can you snip any logs that relate to your hw that is not being recognised or when you press a key if any log shows that pls

some research but relates to non micro controllers
http://www.linux.org/docs/ldp/howto/...y-HOWTO-7.html

you can reduce your tty by adjusting your /etc/inittab.

setserial may be required but so far I can not see the issue.
http://tldp.org/HOWTO/Serial-HOWTO-1...sets_boot_time

changing keys is
http://dev-loki.blogspot.com/2006/04...h-xmodmap.html

however you have not mentioned your hw specs so it may be a laptop thingee....maybe you intend to do a memory card = system cf card install?

http://www.linuxquestions.org/questi...orking-478361/

Thanks for lots of replies aus9,

at first, my linux box is :

cpu: ARM9
mem: 256MB
HDD: over 250GB (rootfs is in sdb2)
kernel: 2.6.16
no display, no keyboard, etc...

no, button a and b are not related.
also they are not keyboard - power and reset.
I just wonder the interrupt works for button a but does not for button b although the micro controller works for both.

in case of button b, no logs as I have tested because the interrupt not occurs
but for button a, I could see the micro controller interrupt :
kernelmon: cmd=micon_interrupts

from dmesg :

By the way, the serial console may affect this problem?

well I know zip about arm hardware.

but you may be right...the kernel or its modules do impact on serio and serial and power functions....but so too does your bios...I assume your system uses the bios?

for example I have mine set to need 4 seconds of continual pressing to do a full shutdown by holding the power button in the bios.

maybe you could have said it was the power button or the reset that was the trouble in the first post? thats why I was thinking you had a keyboard layout error but have wasted your time thinking it.

2) because it is so large...post only the section of your /boot/config if you have such a thing....the kernel config file for this part pls
# Power management options

I am not an expert in this area ....it is possible you are lacking (y for yes or m for modules)
CONFIG_PM=y
CONFIG_ACPI=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y

altho when you read the docs they seem to relate more to suspend and hibernate functions.

Thanks a lot aus9!

my system uses a u-boot in flash mem not the bios.
as I hear you I suspect the power management.
in fact this problem occurs only when got up from sleep mode (so does when sleep mode).
i.e. both buttons work after first boot.
once the system sleep and get up, the interrupt not works for reset button.

this power management is not of the kernel:
something like application.
i.e. sleep mode means the initrd mode with hdd off (initrd is copied to ram disk).
but I think the application is not related to the power management of the kernel.

.config in kernel directory:
the kernel is not changed when sleep or get up.

I hope you realise that "the kernel is not changed when sleep or get up" is never going to change....what you have in the kernel stays in the kernel unless it has force unload kernel setting....modules tho can be moved in and out.

try recompiling kernel to have power management options but I do not know what bootloader you are using....to enable grub or lilo boot parameters....aka cheatcodes