Linus Torvalds wrote: > > On Tue, 6 Mar 2007, Thomas Gleixner wrote: >> SATA has another nice feature. Somehow there is an interrupt pending on >> the SATA controller, which comes in somewhere in the middle of resume. >> If it happens before the SATA code resumed, the SATA code ignores the >> interrupt and the interrupt is disabled due to "nobody cared", which in >> turn prevents SATA to ever become functional again. > > And if you don't want to do any of these things (or are unable to, because > of some ordering constraint or bad design), then you simply need to > unregister and re-register the interrupt handler over sleep. > >> Any idea on that one ? > > Jeff, Auke, does this ring any bells? For the e1000 issue, the problem is solved with Eric Biederman's 3-patch msi cleanups. You should have another message in your mailbox confirming that I tested his patches and the MSI warning for e1000 suspend-resume is gone with them. Cheers, Auke
