From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Shaohua Li <shaohua.li@intel.com>
Cc: Miles Lane <miles.lane@gmail.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, dzickus@redhat.com, ak@suse.de
Subject: Re: [2.6.17-rc5-mm2] crash when doing second suspend: BUG in arch/i386/kernel/nmi.c:174
Date: Tue, 06 Jun 2006 09:23:59 -0700 [thread overview]
Message-ID: <4485AC1F.9050001@goop.org> (raw)
In-Reply-To: <1149576246.32046.166.camel@sli10-desk.sh.intel.com>
Shaohua Li wrote:
> Does below patch help? The nmi suspend/resume doesn't look good to me.
> Only CPU0 uses the suspend/resume code path. Other CPUs run the CPU
> hotplug code path.
>
Unfortunately this just oopses immediately on the first suspend. The
stack trace is unclear (and I'm just going from memory at the moment),
but it looked like it got an invalid op. I'll try to get a clearer idea
of the crash later today.
J
next prev parent reply other threads:[~2006-06-06 16:24 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 22:51 [2.6.17-rc5-mm2] crash when doing second suspend: BUG in arch/i386/kernel/nmi.c:174 Jeremy Fitzhardinge
2006-06-04 11:47 ` Rafael J. Wysocki
2006-06-05 7:21 ` Jeremy Fitzhardinge
2006-06-05 7:37 ` Jeremy Fitzhardinge
2006-06-05 7:48 ` Andrew Morton
2006-06-05 7:59 ` Jeremy Fitzhardinge
2006-06-05 8:35 ` Miles Lane
2006-06-06 6:44 ` Shaohua Li
2006-06-06 14:17 ` Don Zickus
2006-06-06 14:18 ` Andi Kleen
2006-06-06 21:45 ` Don Zickus
2006-06-06 22:15 ` Andrew Morton
2006-06-06 23:05 ` Don Zickus
2006-06-06 23:22 ` Andrew Morton
2006-06-06 23:27 ` Jeremy Fitzhardinge
2006-06-06 23:32 ` Andi Kleen
2006-06-06 23:42 ` Don Zickus
2006-06-08 20:11 ` Pavel Machek
2006-06-06 23:38 ` Nigel Cunningham
2006-06-07 0:06 ` Jeremy Fitzhardinge
2006-06-07 0:13 ` Nigel Cunningham
2006-06-07 0:24 ` Andrew Morton
2006-06-07 0:29 ` Jeremy Fitzhardinge
2006-06-07 0:31 ` Nigel Cunningham
2006-06-07 0:33 ` Andi Kleen
2006-06-07 0:40 ` Nigel Cunningham
2006-06-07 0:26 ` Jeremy Fitzhardinge
2006-06-07 0:33 ` Nigel Cunningham
2006-06-07 0:56 ` Jeremy Fitzhardinge
2006-06-08 20:13 ` Pavel Machek
2006-06-08 12:45 ` Pavel Machek
2006-06-06 23:34 ` Andi Kleen
2006-06-06 23:55 ` Don Zickus
2006-06-07 0:04 ` Andi Kleen
2006-06-07 0:05 ` Nigel Cunningham
2006-06-07 0:42 ` Don Zickus
2006-06-07 0:50 ` Nigel Cunningham
2006-06-07 3:29 ` [linux-pm] " David Brownell
2006-06-07 9:55 ` Rafael J. Wysocki
2006-06-08 20:27 ` Pavel Machek
2006-06-06 16:23 ` Jeremy Fitzhardinge [this message]
2006-06-06 16:51 ` Don Zickus
2006-06-07 2:49 ` Don Zickus
2006-06-07 16:33 ` Andi Kleen
2006-06-07 17:07 ` Jeremy Fitzhardinge
2006-06-07 17:50 ` Don Zickus
2006-06-07 18:53 ` Jeremy Fitzhardinge
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=4485AC1F.9050001@goop.org \
--to=jeremy@goop.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=shaohua.li@intel.com \
/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.