=== ubuntulog [i=ubuntulo@trider-g7.fabbione.net]  has joined #ubuntu-laptop
=== Topic for #ubuntu-laptop: Welcome to the Ubuntu Laptop Team | This is not for support, please use #ubuntu
=== Topic (#ubuntu-laptop): set by Burgwork at Thu Dec 21 22:30:00 2006
=== ThrobbingBrain66 [n=bradley@CPE-24-208-44-208.new.res.rr.com]  has left #ubuntu-laptop ["Ex-Chat"] 
=== crimsun [n=crimsun@dargo.trilug.org]  has joined #ubuntu-laptop
=== kompressor [n=kompress@gw.impilinux.co.za]  has joined #ubuntu-laptop
=== jldugger [n=jldugger@adsl-75-39-128-128.dsl.tpkaks.sbcglobal.net]  has joined #ubuntu-laptop
=== Manny [n=chris@p5496CE2F.dip.t-dialin.net]  has joined #ubuntu-laptop
=== Manny__ [n=chris@p5496D91D.dip.t-dialin.net]  has joined #ubuntu-laptop
=== lmosher [n=lmosher@129-2-134-176.wireless.umd.edu]  has joined #ubuntu-laptop
[06:17] <lmosher> Anyone have tips on why suspend sometimes fails with s2ram? Looking at the logs, it essentially stops (and I have to restart the system manually) after putting CPU1 down. The last message before I reboot is: SMP alternatives: switching to UP code
[06:17] <lmosher> In a good boot the next line is "CPU1 is down" and then "Stopping tasks" so either tasks aren't stopping or my CPU1 isn't going down. Any ideas on how to further debug this?
[06:19] <lmosher> one more thing: it does actually suspend... the power turns off... it just does not resume. On resume I get power, but that's it. The log remains empty until I boot cold.
=== lmosher is trying things. sorry if i disappear :)
=== DarkRaven [n=dvwyngaa@dsl-241-195-175.telkomadsl.co.za]  has joined #ubuntu-laptop
=== DarkRaven [n=dvwyngaa@dsl-244-223-219.telkomadsl.co.za]  has joined #ubuntu-laptop
=== DarkRaven [n=dvwyngaa@dsl-244-223-219.telkomadsl.co.za]  has joined #ubuntu-laptop
=== Kejan [n=cam@pool-72-79-237-92.spfdma.east.verizon.net]  has joined #ubuntu-laptop
=== Kejan [n=cam@pool-72-79-237-92.spfdma.east.verizon.net]  has left #ubuntu-laptop []