> Indeed.I have most excellent news. I was able to get tinyBIOS booting on my development platform. I looked at the problem with the debugger and I think I might have found something. It looks like the interrupt is firing immediately before the clock is enabled. In the handler, we were returning immediately if the clock wasn't enabled (and not clearing the event), so we were caught in a classic interrupt storm. The attached patch rearranges the code so that the handler is installed before we setup the interrupt (so we have somebody to listen to the immediate interrupt), and it makes sure that we clear the event in the IRQ handler regardless of the state of the timer tick. I'm not 100% sure why this happens on IRQ7 but not on 5 or 8, but it might have something to do with the interrupts already being enabled on the other vectors. Anyway, please try this test patch and let me know what happens. Jordan -- Jordan Crouse Systems Software Development Engineer Advanced Micro Devices, Inc.
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Rafael J. Wysocki | Re: Linux 2.6.27-rc5: System boot regression caused by commit a2bd7274b47124d2fc4d... |
git: | |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
