mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jan Spitalnik <lkml@spitalnik.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Disable swsusp on CONFIG_HIGHMEM64
Date: Fri, 6 Jan 2006 14:23:05 +0000	[thread overview]
Message-ID: <20060106142304.GA3269@ucw.cz> (raw)
In-Reply-To: <200601072042.07337.lkml@spitalnik.net>

> > > 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?

It should work in all configurations. I'd like to try fixing
it before disabling it in config.

> > 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?

No clues :-(. I'll try reproducing it locally.

-- 
Thanks, Sharp!

  reply	other threads:[~2006-01-11 12:41 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
2006-01-06 14:23         ` Pavel Machek [this message]
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=20060106142304.GA3269@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@spitalnik.net \
    /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®