Hi!
> >> @@ -663,6 +671,30 @@ static bool is_async(struct device *dev)
> >> }
> >>
> >> /**
> >> + * dpm_drv_timeout - Driver suspend / resume watchdog handler
> >> + * @data: struct device which timed out
> >> + *
> >> + * Called when a driver has timed out suspending or resuming.
> >> + * There's not much we can do here to recover so
> >> + * BUG() out for a crash-dump
> >> + *
> >> + */
> >> +static void dpm_drv_timeout(unsigned long data)
> >> +{
> >> + struct dpm_drv_wd_data *wd_data = (void *)data;
> >> + struct device *dev = wd_data->dev;
> >> + struct task_struct *tsk = wd_data->tsk;
> >> +
> >> + pr_emerg("**** DPM device timeout: %s (%s)\n", dev_name(dev),
> >> + (dev->driver ? dev->driver->name : "no driver"));
> >> +
> >> + pr_emerg("dpm suspend stack:\n");
> >> + show_stack(tsk, NULL);
> >> +
> >> + BUG();
> >> +}
> >
> > So you:
> >
> > dump stack of the suspend task
> It dumps the stack of the suspend task if the suspend callback is run
> synchronously, or the async task if the suspend op is run
> asynchronously.
Lets call that [a]suspend task.
> > do BUG which
> > dumps stack of current task
> > kills current task
> >
> > Current task may very well be idle task; in such case you kill the
> > machine. Sounds like you should be doing something else, like kill -9
> > instead of BUG()?
>
> Not much else you can do, you are stuck part way into suspend with a
> driver's suspend callback half executed. All userspace tasks are
> frozen, and the suspend task is blocked indefinitely.
Yes, there's better option. Attempt killing the [a]suspend task,
instead of killing the current task.
Try putting mdelay(100000) into suspend path. Your patch will do the
wrong thing in that case (actually turning debuggable problem into
undebuggable one).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
