All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Klaus S. Madsen" <ksm@hjernemadsen.org>
Cc: Ingo Molnar <mingo@elte.hu>, Pavel Machek <pavel@ucw.cz>,
	Suspend-devel list <suspend-devel@lists.sourceforge.net>,
	LKML <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Thomas Gleixner <tglx@linutronix.de>,
	Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: Regression in 2.6.25-rc3: s2ram segfaults before suspending
Date: Mon, 03 Mar 2008 12:58:34 -0800	[thread overview]
Message-ID: <47CC667A.9050204@zytor.com> (raw)
In-Reply-To: <20080303205227.GU17932@hjernemadsen.org>

Klaus S. Madsen wrote:
> $ cat /proc/cpuinfo
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 15
> model name      : Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz
> stepping        : 10
> 
> But I'm a bit puzzled by the fact that I'm aparently the only one how
> have encountered the problem? Maybe it's only a problem if one also uses
> PAE? (Thats just a wild guess to explain why I'm the only one seeing
> this).

NX protection only applies to PAE.

	-hpa

  reply	other threads:[~2008-03-03 20:59 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27 22:10 Regression in 2.6.25-rc3: s2ram segfaults before suspending Klaus S. Madsen
2008-02-27 22:19 ` Rafael J. Wysocki
2008-02-27 22:40   ` Pavel Machek
2008-02-28  6:47   ` Klaus S. Madsen
2008-02-28  7:03     ` Pavel Machek
2008-02-28  7:08 ` Klaus S. Madsen
2008-02-28  9:16 ` Ingo Molnar
2008-02-28  9:28   ` Klaus S. Madsen
2008-02-28  9:40     ` Ingo Molnar
2008-02-28 15:04       ` Klaus S. Madsen
2008-02-28 17:52         ` H. Peter Anvin
2008-02-28 19:24           ` Klaus S. Madsen
2008-02-28 19:31             ` H. Peter Anvin
2008-02-28 19:49               ` Klaus S. Madsen
2008-02-28 22:45                 ` H. Peter Anvin
2008-02-29  7:00                   ` Klaus S. Madsen
2008-02-29 21:05                     ` H. Peter Anvin
2008-02-29 21:26                       ` Ingo Molnar
2008-03-01  9:45                         ` Klaus S. Madsen
2008-03-01 19:53                           ` H. Peter Anvin
2008-03-03 12:17                           ` Pavel Machek
2008-03-03 15:11                             ` Klaus S. Madsen
2008-03-03 17:48                               ` Ingo Molnar
2008-03-03 17:53                                 ` H. Peter Anvin
2008-03-03 20:52                                 ` Klaus S. Madsen
2008-03-03 20:58                                   ` H. Peter Anvin [this message]
2008-03-03 21:05                                   ` Pavel Machek
2008-03-03 21:06                                     ` Matthew Garrett
2008-03-03 21:06                                     ` Pavel Machek
2008-03-03 21:21                                       ` Klaus S. Madsen
2008-03-04 12:36                                   ` Ingo Molnar
2008-03-04 21:58                                     ` Klaus S. Madsen
2008-03-04 22:08                                       ` H. Peter Anvin
2008-03-04 23:00                                     ` Jeremy Fitzhardinge
2008-03-04 23:11                                       ` H. Peter Anvin
2008-03-04 23:21                                         ` Jeremy Fitzhardinge
2008-03-04 23:30                                         ` Matthew Garrett
2008-03-04 12:42                                   ` Ingo Molnar
2008-03-03 15:40                             ` Rafael J. Wysocki
2008-03-03 17:10                             ` H. Peter Anvin
2008-03-03 17:47                               ` Pavel Machek
2008-03-03 17:50                                 ` H. Peter Anvin
2008-03-03 17:53                               ` Ingo Molnar
2008-03-03 17:58                                 ` H. Peter Anvin
2008-03-01  1:18                       ` Rafael J. Wysocki

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=47CC667A.9050204@zytor.com \
    --to=hpa@zytor.com \
    --cc=ksm@hjernemadsen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mjg59@srcf.ucam.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=suspend-devel@lists.sourceforge.net \
    --cc=tglx@linutronix.de \
    /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.