> are you really sure? in my system (laptop with core duo cpu) it is > increased by around 1000-2000 every 2 seconds and AFAIK it is using > HPET. > Yes. How can I see the timer is i8253 or HPET? I just found 'timer' in terms of the output of 'cat /proc/interrupts'. > So maybe IMO free_irq() is causing your cpu referencing null > instruction...that might be due to free_irq is not checking whether it > is safe to delete a handler.... > After enabling the RTC support, I have recompiled the kernel and try to use the irq 8. But, it seems that the 'irq_request()' can not register my hangler. 2011/8/28 Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>: > Hi... > > On Sat, Aug 27, 2011 at 22:23, Parmenides <mobile.parmenides@xxxxxxxxx> wrote: >> I wonder how an interrupt handler work, and so try to make one by >> myself. The first problem is which irq number should I select to hook >> an interrupt handler on it. In terms of the following messages, I >> think irq 0 can be adopted because the number of interrupts raised >> remains 145 and does not increase any more. > > are you really sure? in my system (laptop with core duo cpu) it is > increased by around 1000-2000 every 2 seconds and AFAIK it is using > HPET. > > So maybe IMO free_irq() is causing your cpu referencing null > instruction...that might be due to free_irq is not checking whether it > is safe to delete a handler.... > > -- > regards, > > Mulyadi Santosa > Freelance Linux trainer and consultant > > blog: the-hydra.blogspot.com > training: mulyaditraining.blogspot.com > _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
