I so for some days two new patches. Thirst one may help you ( pcmcia:
irq probe can be done without risking an IRQ storm):

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=42c59208219a2d43f0dde94bebc68c20b95b13ce

author
Linus Torvalds
<email address hidden>

Mon, 14 Jul 2008
20:24:39 +0000 (13:24
-0700)
committer
Linus Torvalds
<email address hidden>

Mon, 14 Jul 2008
20:24:39 +0000 (13:24
-0700)
commit
42c59208219a2d43f0dde94bebc68c20b95b13ce
tree
ff20941f83a92ffb4224c95ddee9b7eb225ed958
tree | snapshot
parent
dddec01eb8e2b56267b37a6f9f0997a64b4e0b2a
commit | diff
parent
727c6742c29e46177951fdc8f6758085e03bb981
commit | diff
Merge git://git./linux/kernel/git/brodo/pcmcia-2.6

* git://git.kernel.org/pub/scm/linux/kernel/git/brodo/pcmcia-2.6: (23 commits)
  pcmcia: Fix ide-cs sparse warning
  pcmcia: ide-cs debugging bugfix
  pcmcia: allow for longer CIS firmware files
  pcmcia: cm40x0 cdev lock_kernel() pushdown
  pcmcia: (re)move {pcmcia,pccard}_get_status
  pcmcia: kill IN_CARD_SERVICES
  pcmcia: Remove unused header file code
  pcmcia: remove unused bulkmem.h
  pcmcia: simplify pccard_validate_cis
  pcmcia: carve out ioctl adjust function to pcmcia_ioctl
  pcmcia: irq probe can be done without risking an IRQ storm
  pcmcia: Fix ti12xx_2nd_slot_empty always failing
  pcmcia: check for pointer instead of pointer address
  pcmcia: switch cm4000_cs.c to unlocked_ioctl
  pcmcia: simplify rsrc_nonstatic attributes
  pcmcia: add support CompactFlash PCMCIA support for Blackfin.
  pcmcia: remove version.h
  pcmcia: cs: kill thread_wait
  pcmcia: i82365.c: check request_irq return value
  pcmcia: fix Alchemy warnings

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1adb0850a1254333d81e64121c80af100c6d6e06


author
Thomas Gleixner
<email address hidden>

Mon, 28 Apr 2008
15:01:56 +0000 (17:01
+0200)
committer
Thomas Gleixner
<email address hidden>

Fri, 2 May 2008 11:40:34
+0000 (13:40 +0200)
commit
1adb0850a1254333d81e64121c80af100c6d6e06
tree
61835b06e78eb6f556c038ceabc706440f339d3a
tree | snapshot
parent
886c35fbcf6fb2eee15687efc2d64d99b6ad9a4a
commit | diff
genirq: reenable a nobody cared disabled irq when a new driver arrives

Uwe Kleine-Koenig has some strange hardware where one of the shared
interrupts can be asserted during boot before the appropriate driver
loads. Requesting the shared irq line from another driver result in a
spurious interrupt storm which finally disables the interrupt line.

I have seen similar behaviour on resume before (the hardware does not
work anymore so I can not verify).

Change the spurious disable logic to increment the disable depth and
mark the interrupt with an extra flag which allows us to reenable the
interrupt when a new driver arrives which requests the same irq
line. In the worst case this will disable the irq again via the
spurious trap, but there is a decent chance that the new driver is the
one which can handle the already asserted interrupt and makes the box
usable again.

Eric Biederman said further: This case also happens on a regular basis
in kdump kernels where we deliberately don't shutdown the hardware
before starting the new kernel.  This patch should reduce the need for
using irqpoll in that situation by a small amount.

Signed-off-by: Thomas Gleixner <email address hidden>
Tested-and-Acked-by: Uwe Kleine-König <email address hidden>