Robert Hancock wrote: > Tejun Heo wrote: >> Tejun Heo wrote: >>> Robert Hancock wrote: >>>> Tejun Heo wrote: >>>>> Tejun Heo wrote: >>>>>>> [ 34.466899] testing NMI watchdog ... <4>WARNING: CPU#0: NMI >>>>>>> appears >>>>>>> to be stuck (0->0)! >>>>>>> [ 34.555056] WARNING: CPU#1: NMI appears to be stuck (0->0)! >>>>>> Oops, missed that. I'll see whether there's IRQ storm going on. >>>>> I made the nv irq handler to print message every 100th time and it >>>>> says >>>>> nothing after lock up and no response to keyboard, sysrq or >>>>> serial. It >>>>> seems like a solid lock up to me. Anything else you want me to try >>>>> out? >>>> I assume that replugging or unplugging cables after that point doesn't >>>> bring it back to life? >>> Nope. The machine is a solid brick. >>> >> >> If you want, I can ship the board + processor + cooler to you for >> debugging. I guess it will be more useful in your hands than mine. > > If it's an A8N-E I'd be surprised if it behaved differently from my > A8N-SLI Deluxe, though maybe it's a different chipset revision or > something.. The last time I tested hotplug on here it seemed to work > fine, though I haven't done any rapid disconnect/reconnect tests. > > How about putting a bunch of printks inside the interrupt handler? That > would tell us if it's even reaching the interrupt handler.. If you give me a patch, I'll apply it and cause lock up and report the result. Just shoot the patches my way. But maybe reproducing the lock up on your machine would be the better solution. It isn't difficult at all. Plug in, fire up IO, disconnect, wait. Connect different drive. Rinse and repeat. It will lock up pretty soon. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
