mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Spitalnik <lkml@spitalnik.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Disable swsusp on CONFIG_HIGHMEM64
Date: Sat, 07 Jan 2006 20:42:07 +0100	[thread overview]
Message-ID: <200601072042.07337.lkml@spitalnik.net> (raw)
In-Reply-To: <20060106043019.GA2545@ucw.cz>

Dne pátek 06 leden 2006 05:30 Pavel Machek napsal(a):
> On Sat 07-01-06 16:04:03, Jan Spitalnik wrote:
> > Dne pátek 06 leden 2006 00:43 Pavel Machek napsal(a):
> > > On Fri 06-01-06 19:45:09, Jan Spitalnik wrote:
> > > > Hello,
> > > >
> > > > suspending to disk is not supported on CONFIG_HIGHMEM64G setups
> > > > (http://suspend2.net/features). Also suspend to ram doesn't work.
> > > > This patch
> > >
> > > NAK. suspend2.net describes very different code.
> >
> > Well, I was using suspend2.net's page just as reference, to point out the
> > fact that HIGHMEM is on both suspend "platforms" supported only up to 4G.
> > I was not refering to suspend2's actual features, but rather swsusp's (or
> > what's the proper name for suspend1 code). So i guess the patch still
> > holds, no?
>
> No.

Could you be please more specific? Is there some list of swsusp's features? 
swsusp.txt says that it "A: It should work okay with highmem." Does that mean 
both possible highmem configurations?

>
> > > > fixes Kconfig to disallow such combination. I'm not 100% sure about
> > > > the ACPI_SLEEP part, as it might be disabling some working setup -
> > > > but i think that s2r and s2d are the only acpi sleeps allowed, no?
> > >
> > > s2ram probably works. Try getting it working without highmem64,
> > > then turn it on.
> >
> > It works with HIGHMEM but not HIGHMEM64G. You can find the oops from
> > HIGHMEM64G below. It crashes very reliably on little stress after resume.
>
> s2ram should not depend on ammount of memory. Try debugging
> it, but do not disable feature just because it does not work
> for you. I'd start with minimum drivers...

Well, I've tried it with the bare minimum that was needed to run the system, 
but it did the same. I'm sorry but i lack the knowledge to properly debug it 
on source level.  Do you see something that perhaps i don't see in the oops? 
Maybe some clues as what might be going wrong?

Thanks,

-- 
Jan Spitalnik
jan@spitalnik.net

  reply	other threads:[~2006-01-07 19:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06 18:45 Jan Spitalnik
2006-01-05 23:43 ` Pavel Machek
2006-01-07 15:04   ` Jan Spitalnik
2006-01-06  4:30     ` Pavel Machek
2006-01-07 19:42       ` Jan Spitalnik [this message]
2006-01-06 14:23         ` Pavel Machek
2006-01-08 13:34         ` Pavel Machek
2006-01-08 14:16         ` Pavel Machek
2006-01-08 15:52         ` Pavel Machek

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=200601072042.07337.lkml@spitalnik.net \
    --to=lkml@spitalnik.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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

all inboxes | Powered by JetHome®