Hi, * Jonathan Kotta <jpkotta@xxxxxxxxx> [080227 12:24]: > I'm using 2.6.24.2 on an omap5912osk. I have a reproducible problem, > where somehow irq 159 keeps occurring. I can't find anywhere where > it's enabled, or what it could be in the hardware, and it appears to > be initialized with a default isr that just prints debug info. The > way I can trigger this is to run the program "gpe-life" from a script. > Strangely, it does not happen when I run gpe-life from the prompt. > It does not happen when I use 2.6.22. > > irq 159, desc: c034bd50, depth: 1, count: 0, unhandled: 0 > ->handle_irq(): c006d420, handle_bad_irq+0x0/0x238 > ->chip(): c034eb08, 0xc034eb08 > ->action(): 00000000 > IRQ_DISABLED set > IRQ_NOPROBE set > IRQ_NOREQUEST set > > [root@omap5912osk:~]$ cat /proc/interrupts > CPU0 > 19: 0 MPU DMA > 20: 0 MPU DMA > 21: 0 MPU DMA > 22: 0 MPU DMA > 23: 0 MPU DMA > 24: 0 MPU DMA > 25: 230236 MPU LCD DMA > 31: 5 MPU lcdc > 33: 1 MPU omap-keypad > 36: 4536 MPU i2c_omap > 38: 1 MPU ohci_hcd:usb1 > 44: 0 MPU McBSP > 45: 0 MPU McBSP > 46: 617 MPU serial > 54: 465033 MPU 32KHz timer > 57: 0 MPU rtc0 > 58: 0 MPU rtc0 > 78: 0 MPU peripheral wakeup > 85: 0 MPU DMA > 86: 0 MPU DMA > 87: 0 MPU DMA > 88: 0 MPU DMA > 89: 0 MPU DMA > 90: 0 MPU DMA > 91: 0 MPU DMA > 92: 0 MPU DMA > 93: 0 MPU DMA > 94: 0 MPU DMA > 160: 2707 GPIO eth0 > 164: 0 GPIO ads7846 > 178: 0 GPIO serial wakeup > 197: 0 GPIO serial wakeup > 209: 465825 GPIO serial wakeup > 222: 78 GPIO omap_cf, ide0 > 353: 0 MPUIO tps65010 > 354: 0 MPUIO mistral_wakeup > Err: 0 That souds like it's the gpio bank1 interrupt (INT_GPIO_BANK1), maybe recent gpio handling changes broke something? Toiny -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
