Messages in this thread | | | From | Jan Rychter <> | Subject | Re: 2.6.9-rc2-mm1 swsusp bug report. | Date | Mon, 11 Oct 2004 03:17:09 +0900 |
| |
>>>>> "Pavel" == Pavel Machek <pavel@ucw.cz> writes: Pavel> Hi! > The problem isn't really that you're out of memory. Rather, the > memory is so fragmented that swsusp is unable to get an order 8 > allocation in which to store its metadata. There isn't really > anything you can do to avoid this issue apart from eating memory > (which swsusp is doing anyway). >> >> That's one megabyte, right? Can't we preallocate that on boot, while >> there's still chance to get that much contiguous memory? If the user >> has swsusp compiled into his kernel, he probably wants it to >> function, so it's not really "wasted".
Pavel> You do not know how much you should preallocate, because it Pavel> depends on ammount of memory used. You could preallocate maximum Pavel> possible ammount...
Pavel> OTOH this is first report of this failure. If it fails once in a Pavel> blue moon, it is probably better to let it fail than waste Pavel> memory.
This is *exactly* why I choose to use swsusp2. There is a marked difference in the maintainer's approach to these kinds of problems.
The net result is that swsusp2 has worked for me very well for many months now: I have been suspending and resuming happily for several months, with exactly 0 swsusp-caused crashes or failures.
BTW, on a related note, I believe there is too much acceptance for crashes and failures in the Linux world recently. Take an example: I can bring down any of my machines (kernels 2.4 or 2.6) in less than 10 minutes just by plugging in and unplugging USB devices. There is something fundamentally wrong with the USB subsystem if it is possible to do that.
--J.
- 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/
| |