linux-kernel - TIMER0 interrupt's problem in kernel 2.6.21 ( realview-smp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <ab40e9c0708181834y7804a961p2c48a32a78fae688@mail.gmail.com>
Date:	Sun, 19 Aug 2007 03:34:45 +0200
From:	"Xu Yang" <risingsunxy@...glemail.com>
To:	linux-kernel@...r.kernel.org
Subject: TIMER0 interrupt's problem in kernel 2.6.21 ( realview-smp_defconfig)

I am running kernel 2.6.21 on my realview_eb_mpcore system.

at the beginning I found the program is stuck at calibrating
loop................, this is because that the timer0 didn't give out
any interrupt.

after enable the timer0's interrupt, I found that even when there is
no timer interrupt the interrupt routine (realview_timer_interrupt()
)is still reached.

I added a timer interrupt disable instruction in the routine
realview_timer_interrupt() , which makes sure that after the first
interrupt the interrupt would be disabled. even in this situation , I
can still see that the interrupt routine is accessed by the cpu.

I guess this maybe caused by the problem of the gic_ack() or some
other functions?

does anyone ever meet such a situation?

anyone knows how to handle this?

any idea is  appreciated.

regards,

Yang
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/