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: Sat, 6 Aug 2011 21:36:59 +0200 [thread overview]
Message-ID: <201108062136.59218.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1108051641040.2055-100000@iolanthe.rowland.org>
On Friday, August 05, 2011, Alan Stern wrote:
> On Fri, 5 Aug 2011, Rafael J. Wysocki wrote:
>
> > > 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().
> >
> > OTOH, I'm not sure how pci_legacy_suspend_late() was called.
> > In theory it is only called by the system suspend code and it surely
> > is not called for e1000e.
>
> The ? indicates that pci_legacy_suspend_late() wasn't necessarily on
> the task's call stack; it may simply have been a leftover pointer from
> some other operation, sitting somewhere in the middle of the stack
> page.
However, Jesper said the crash happend during suspend, so I wonder how
that might be present on the stack while executing runtime PM routines?
Rafael
prev parent reply other threads:[~2011-08-06 19:35 UTC|newest]
Thread overview: 12+ 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 20:01 ` [linux-pm] " Alan Stern
2011-08-05 20:13 ` Rafael J. Wysocki
2011-08-05 20:21 ` Alan Stern
2011-08-05 20:30 ` Rafael J. Wysocki
2011-08-05 20:36 ` Rafael J. Wysocki
2011-08-05 20:44 ` 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-06 19:36 ` Rafael J. Wysocki [this message]
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=201108062136.59218.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox