dmesg output is added. increasing CONFIG_BLK_DEV_RAM_SIZE from 7777 to 131072 hasn't changed the non-functioning of 2.6.24-rc3
s2disk works with 2.6.23.8 ; I tested 4 cycles in a row, 2 from console and 2 from within X Chris On Mon, 19 Nov 2007 19:58:36 +0100 "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote: > On Monday, 19 of November 2007, Chris Friedhoff wrote: > > Hallo Rafael, > > > > just to let you know: with 2.6.24-rc3 I have the same problem. > > Thanks. > > > On Sun, 11 Nov 2007 19:45:06 +0100 > > "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote: > > > > > On Saturday, 10 of November 2007, Chris Friedhoff wrote: > > > > please cc me, I'm not not subscribed to LKML > > > > > > > > Hello, > > > > > > > > with kernel 2.6.24-rc2 STD with s2disk suspends the system to disk, but > > > > when I start the system and the suspended systemimage is loaded, it > > > > fails to "activate" this suspended systemimage and continues after some > > > > time with following the normal boot sequence. > > Please add the dmesg output taken right after that as an attachment to the > bugzilla entry at http://bugzilla.kernel.org/show_bug.cgi?id=9345 > > Thanks, > Rafael -------------------- Chris Friedhoff [EMAIL PROTECTED] - 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/
