All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Wolf <wwolf@vt.edu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: AMD64 Swsusp on 2.6.9-rc4-mm1
Date: Tue, 16 Nov 2004 12:43:00 -0600	[thread overview]
Message-ID: <1100630580.18017.4.camel@Xnix> (raw)
In-Reply-To: <200410171224.14434.rjw@sisk.pl>

On Sun, 2004-10-17 at 12:24 +0200, Rafael J. Wysocki wrote:
> On Tuesday 16 of November 2004 08:19, William Wolf wrote:
> > Is this supposedly something new in rc4-mm1?  I have been having the
> > same problems since around 2.6.8.1, though i havent gone through every
> > single -mm patch, i have tried at least one in every -rcx candidate, and
> > they have all done this same thing.
> 
> This may be for another reason.  I generally test all of the -rc and -mm 
> patches on an AMD64 box and apparently 2.6.9-rc4-mm1 is the first one that 
> has the problem I was talking about.  AFAICT, the other kernels may fail in a 
> similar way if memory is stuffed with something (eg after updatedb).

Hmmm, ok, well I can boot into other -rcx-mmx kernels and get my output
if that would help any. Usually when i test, i try it immediately after
booting and logging into a console (no X running), so it would be tough
for the memory to be stuffed.


      reply	other threads:[~2004-10-17 11:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-16 20:47 AMD64 Swsusp on 2.6.9-rc4-mm1 William Wolf
2004-10-16 20:52 ` Rafael J. Wysocki
2004-11-16  7:19   ` William Wolf
2004-10-17 10:24     ` Rafael J. Wysocki
2004-11-16 18:43       ` William Wolf [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=1100630580.18017.4.camel@Xnix \
    --to=wwolf@vt.edu \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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.