Messages in this thread | | | Date | Sun, 8 Jan 2006 16:52:45 +0100 | From | Pavel Machek <> | Subject | Re: [PATCH] Disable swsusp on CONFIG_HIGHMEM64 |
| |
> > > > 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?
HIGHMEM64G breaks boot on my thinkpad (pretty recent git). I guess I'm not solving this one. Pavel -- 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/
| |