On Mon, 2009-10-26 at 14:57 -0700, Alexander Beregalov wrote: > 2009/10/26 Rafael J. Wysocki <r...@sisk.pl>: > > This message has been generated automatically as a part of a report > > of recent regressions. > > > > The following bug entry is on the current list of known regressions > > from 2.6.31. Please verify if it still should be listed and let me know > > (either way). > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14375 > > Subject : Intel(R) I/OAT DMA Engine init failed > > Submitter : Alexander Beregalov <a.berega...@gmail.com> > > Date : 2009-10-02 9:46 (25 days old) > > References : http://marc.info/?l=linux-kernel&m=125447680016160&w=4 > > Handled-By : Dan Williams <dan.j.willi...@intel.com> > > Patch : http://patchwork.kernel.org/patch/51808/ > > When I patch reiserfs the bug goes to libata, it means ioatdma works > and libata does not. It looks like inaccurate work with memory > somewhere, but I do not know how to find it. > I cannot reproduce it since 2.6.32-rc3 and I do not see any bugs since then.
If it helps the debug, the symptom seems to be that all interrupts get turned off. Neither the normal device completion interrupt nor the completion watchdog timer fire before the self test timeout. It seems something else re-enables interrupts eventually, but we know they were at least disabled for 3 seconds. An unmatched spin_unlock_irq in an async initialization path perhaps? -- Dan -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
