Pc not waking up after Kunbuntu add/remove

[Werner Schram]

Adam Petty wrote:
> On Sat, Dec 19, 2009 at 5:33 PM, Werner Schram <wrschram at gmail.com> wrote:
>   
>> Adam Petty wrote:
>>     
>>> Ok I was wrong about the numlock. It did not turn on/off and I tried
>>> remoting and got nothing
>>>
>>> Here is what I was able to get from the Kern.log looks like it locked @ 14:23:13
>>>
>>> Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020661] "echo 0 >
>>> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
>>> Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020665] i915/0        D
>>> 0000000000000000     0   300      2 0x00000000
>>>
>>>       
>> The second message refers to i915, which is the name of a module for a
>> intel video adapter, so that would be the one that crashed. The first
>> message seems to refer to an earlier message about a hung task. Is there
>> some more information about that in the log file? Is there something
>> relevant in /var/log/messages around 14:23?
>>
>> Werner
>>
>>     
>
> Its mostly the same error until 13:16 Then this
>
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110480] Mem-Info:
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110483] Node 0 DMA per-cpu:
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110487] CPU    0: hi:
> 0, btch:   1 usd:   0
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110490] CPU    1: hi:
> 0, btch:   1 usd:   0
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110492] Node 0 DMA32 per-cpu:
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110496] CPU    0: hi:
> 186, btch:  31 usd: 178
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110499] CPU    1: hi:
> 186, btch:  31 usd:  78
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110504]
> Active_anon:302882 active_file:180 inactive_anon:100904
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110506]  inactive_file:93
> unevictable:0 dirty:0 writeback:0 unstable:0
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110507]  free:3436
> slab:16808 mapped:3935 pagetables:6704 bounce:0
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110510] Node 0 DMA
> free:8028kB min:40kB low:48kB high:60kB active_anon:5972kB
> inactive_anon:1728kB active_file:12kB inactive_file:0kB
> unevictable:0kB present:15316kB pages_scanned:0 all_unreclaimable? no
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110517] lowmem_reserve[]:
> 0 1994 1994 1994
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110524] Node 0 DMA32
> free:5716kB min:5692kB low:7112kB high:8536kB active_anon:1205556kB
> inactive_anon:401888kB active_file:708kB inactive_file:372kB
> unevictable:0kB present:2042536kB pages_scanned:260 all_unreclaimable?
> no
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110531] lowmem_reserve[]: 0 0 0 0
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110537] Node 0 DMA: 9*4kB
> 3*8kB 6*16kB 2*32kB 2*64kB 0*128kB 2*256kB 2*512kB 2*1024kB 2*2048kB
> 0*4096kB = 8028kB
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110552] Node 0 DMA32:
> 385*4kB 2*8kB 4*16kB 1*32kB 2*64kB 1*128kB 1*256kB 1*512kB 1*1024kB
> 1*2048kB 0*4096kB = 5748kB
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110567] 60501 total pagecache pages
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110570] 0 pages in swap cache
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110572] Swap cache stats:
> add 0, delete 0, find 0/0
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110575] Free swap  = 0kB
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.110577] Total swap = 0kB
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.118127] 521809 pages RAM
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.118130] 9927 pages reserved
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.118132] 29411 pages shared
> Dec 19 13:16:55 Kitchen-Linux kernel: [ 2503.118134] 482210 pages non-shared
>
> Do I not have a swap file?
>   
It looks like it. Does /etc/fstab have a line like this?
UUID=1ed76686-5524-43d4-bf8b-17595ac39f7e none            swap    
sw              0       0
or
/dev/hda2        none            swap    sw              0       0

and what is the output of the commands:

sudo fdisk -l

and:

sudo blkid

I just googled for simmilar log messages. It looks like what you just 
posted is the end of a stack trace of a 'page allocation failure' 
message. Which is likely related to the absence of your swap, and could 
be the cause of your suspend problems.

Werner