On Wednesday, 11 April 2007 12:45, Jiri Slaby wrote: > Rafael J. Wysocki napsal(a): > > On Wednesday, 11 April 2007 09:36, Jiri Slaby wrote: > >> Rafael J. Wysocki napsal(a): > >>> On Monday, 9 April 2007 22:07, Jiri Slaby wrote: > >>>> I have bad news for you :(. I thought I had unpatched kernel, but it > >>>> happens > >>>> in -rc6 too. > >>> I guess you mean you're still seeing the 'not enough memory to suspend' > >>> problem? > >> Yes: > >> Disabling non-boot CPUs ... > >> kvm: disabling virtualization on CPU1 > >> Breaking affinity for irq 9 > >> CPU 1 is now offline > >> SMP alternatives: switching to UP code > >> CPU1 is down > >> swsusp: critical section: > >> swsusp: Need to copy 158309 pages > >> swsusp: Not enough free memory > >> Error -12 suspending > >> Enabling non-boot CPUs ... > >> SMP alternatives: switching to SMP code > >> Booting processor 1/2 APIC 0x1 > >> Initializing CPU#1 > > > > How reproducible is it? I'm going to try to reproduce it on one of my > > boxes. > > My tip is one of three cases: after some work on fresh boot -- some > consumers such as thunderbird, firefox, 10 or so terminals with > gnome-session. Single xterm + gnome-session semms not to be a problem.
Does the workaround with setting the image size below 1/2 of RAM work for you? Rafael - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
