[lkml]   [2009]   [Jan]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: What should PCI core do during suspend-resume? (was: Re: 2.6.29-rc3: tg3 dead after resume)

On Sat, 31 Jan 2009, Linus Torvalds wrote:
> But how many people test STR while doing a "ping -f" from another machine?
> It _should_ work. Do you guarantee that it does?

Btw, this really only is interesting if there's a shared interrupt.

I'm sure that there are network drivers that will crash even on their own
with _just_ the right timing (imagine having a delayed interrupt pending,
then doing the "pci_set_power_state(PCI_D3hot)" thing, and then get the
interrupt handler invoked on another CPU _just_ afterwards), but it's
probably really hard to trigger, and a bug in that specific driver anyway.

But what's much more interesting (and not necessarily a driver bug, but a
general PM infrastructure problem) is if we have that shared interrupt
case, and the network driver gets lots of interrupts just as "driver X" is
shutting down with that interrupt shared. Then, "driver X" will get
interrupts after the PM layer has put its device to sleep, and now "driver
X" is quite understandably confused - it didn't even do the "put to sleep"
itself, but now its device is no longer responding.

And now it's not a really unlikely race condition any more.


 \ /
  Last update: 2009-02-01 00:43    [W:0.119 / U:0.816 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site