All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Jesper Juhl <jj@chaosbits.net>, Len Brown <len.brown@intel.com>,
	linux-pm@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-pm] Crash when suspending Lenovo T510 laptop (2.6.39.3)
Date: Fri, 5 Aug 2011 22:30:48 +0200	[thread overview]
Message-ID: <201108052230.48862.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1108051617430.2055-100000@iolanthe.rowland.org>

On Friday, August 05, 2011, Alan Stern wrote:
> On Fri, 5 Aug 2011, Rafael J. Wysocki wrote:
> 
> > > > I don't know how to fix it yet, but I think I know what the problem is.
> > > > Namely, a runtime suspend of the Ethernet adapter as occured in parallel with
> > > > the system-wide suspend and they clashed.  The runtime suspend has probably
> > > > been provoked by detaching the Ethernet cable from the box.
> > > 
> > > For them to clash in that way would mean that the PM workqueue didn't
> > > get frozen.
> > 
> > Not necessarily, I think.  It's sufficient that system suspend is started
> > while the runtime PM operation is in progress.
> 
> How so?  The system suspend doesn't call down to the subsystems or 
> drivers until after all the threads are frozen.  In this case the stack 
> dump shows that the runtime PM operation was asynchronous, running in a 
> workqueue thread (pm_runtime_work is one of the routines near the end 
> of the stack dump).  The thread wouldn't have frozen until the runtime 
> PM operation was complete.

You're right, sorry.  System suspend was not involved, so the problem
was triggerend by runtime suspend alone, resulting from unplugging the
Ethernet cable.

It looks like the crash started in pci_disable_msi().

Thanks,
Rafael

  reply	other threads:[~2011-08-05 20:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05  0:47 Crash when suspending Lenovo T510 laptop (2.6.39.3) Jesper Juhl
2011-08-05 19:18 ` Rafael J. Wysocki
2011-08-05 19:18 ` Rafael J. Wysocki
2011-08-05 20:01   ` [linux-pm] " Alan Stern
2011-08-05 20:13     ` Rafael J. Wysocki
2011-08-05 20:13     ` [linux-pm] " Rafael J. Wysocki
2011-08-05 20:21       ` Alan Stern
2011-08-05 20:21       ` [linux-pm] " Alan Stern
2011-08-05 20:30         ` Rafael J. Wysocki [this message]
2011-08-05 20:36           ` Rafael J. Wysocki
2011-08-05 20:36           ` [linux-pm] " Rafael J. Wysocki
2011-08-05 20:44             ` Alan Stern
2011-08-05 20:44             ` [linux-pm] " Alan Stern
2011-08-06  8:56               ` Jesper Juhl
2011-08-09 12:27                 ` Jesper Juhl
2011-08-09 14:23                   ` Alan Stern
2011-08-09 14:23                   ` [linux-pm] " Alan Stern
2011-08-09 12:27                 ` Jesper Juhl
2011-08-06  8:56               ` Jesper Juhl
2011-08-06 19:36               ` Rafael J. Wysocki
2011-08-06 19:36               ` [linux-pm] " Rafael J. Wysocki
2011-08-05 20:30         ` Rafael J. Wysocki
2011-08-05 20:01   ` Alan Stern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201108052230.48862.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=jj@chaosbits.net \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.