On Mon, 25 May 2009 13:25:55 +0100, David <david@xxxxxxxxxxxxxxx> wrote: > >> I wonder if CONFIG_HAVE_DMA_API_DEBUG does it (enabled with a select > >> in arch/x86/Kconfig). Strange that it started happening now. > >> > > That is enabled. I'll switch it off and give it another go. > > > While CONFIG_HAVE_DMA_API_DEBUG was set, DMA_API_DEBUG was not, so I > guess there's nothing I can do to test? I suppose so. I misunderstood how this worked. I guessed that the DMA API debugging was the culprit because its introduction coincided with the recent onset of this oops. Although usbmon does essentially illegal tricks to look at data already mapped for DMA, the code used to work for a few releases. Bisecting may help. I cannot be sure of it though, and it's going to take a lot of reboots. Unfortunately, although I have an Opteron, the issue does not occur here, so I'm at a loss for the moment. But I'll have to tackle it somehow. Not sure how though. Any suggestions are welcome. -- Pete -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
