Messages in this thread | | | Date | Fri, 6 Jan 2006 14:23:05 +0000 | From | Pavel Machek <> | Subject | Re: [PATCH] Disable swsusp on CONFIG_HIGHMEM64 |
| |
> > > 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! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |