Pc not waking up after Kunbuntu add/remove

[Adam Petty]

On Sat, Dec 19, 2009 at 10:29 AM, Adam Petty <linux at papettys.com> wrote:
> On Sat, Dec 19, 2009 at 9:10 AM, Aart Koelewijn <aart at mtack.xs4all.nl> wrote:
>> On Sat, 19 Dec 2009 07:49:24 -0500, Adam Petty wrote:
>>
>>> On Fri, Dec 18, 2009 at 4:59 PM, Werner Schram <wrschram at gmail.com>
>>> wrote:
>>>> Hi Adam,
>>>>
>>>> Adam Petty wrote:
>>>>> I thought I sent this yesterday but I dont think it went through.
>>>>> Either that or I am being ignored as a loser newbie :)
>>>>>
>>>> Nope, this list doesn't have any losers, but it seems it also doesn't
>>>> have any people that have experience with suspend mode problems after
>>>> deinstalling kubuntu ;)
>>>>> After I installed kunbuntu then removed it, may pc does not comeback
>>>>> from suspend mode all the time. I have to do a hard boot to get it
>>>>> back. Any ideas?
>>>>>
>>>> Which OS is it that isn't suspending, and which version is it? How did
>>>> you remove kubuntu? Could you post the messages from your log files
>>>> from around the time at which you suspended? You should look at
>>>> /var/log/messages and /var/log/kern.log, You can open them with any
>>>> text editor.
>>>>
>>>> Werner
>>>>
>>>>
>>> Yeah I guess some more info might have been helpful. I have Ubuntu 9.10
>>> and that is the OS I have the issue with. I removed Kubuntu  it using a
>>> a command I found here
>>>
>>> http://www.psychocats.net/ubuntu/puregnome
>>>
>>> The problem with the logs is that I dont know exactly when the problem
>>> occurs, Its usually after leaving the computer on over night or when I
>>> come back from work. So it could could be anywhere from 6-9 hours. And
>>> the old numlock test work the lights turn on and off, there just isn't
>>> any display. the optical mouse has 'light'. So maybe it is coming back
>>> just not turning on the display?
>>
>> Could you try to log-in from another computer with ssh. You then might be
>> able to diagnose the problem.
>>
>> Aart
>>
>
> Didnt think of that. Duh.
>

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
Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020672]  ffff880079debd70
0000000000000046 0000000000000000 0000000000015880
Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020678]  ffff88007a96de70
0000000000015880 0000000000015880 0000000000015880
Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020684]  0000000000015880
ffff88007a96de70 0000000000015880 0000000000015880
Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020690] Call Trace:
Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020703]
[<ffffffff815286a7>] __mutex_lock_slowpath+0xd7/0x160
Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020708]
[<ffffffff815285a6>] mutex_lock+0x26/0x50
Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020739]
[<ffffffffa00618d8>] i915_gem_retire_work_handler+0x38/0x90 [i915]
Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020756]
[<ffffffffa00618a0>] ? i915_gem_retire_work_handler+0x0/0x90 [i915]
Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020764]
[<ffffffff810737a5>] run_workqueue+0x95/0x170
Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020769]
[<ffffffff81073924>] worker_thread+0xa4/0x120
Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020774]
[<ffffffff81078b30>] ? autoremove_wake_function+0x0/0x40
Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020779]
[<ffffffff81073880>] ? worker_thread+0x0/0x120
Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020784]
[<ffffffff81078746>] kthread+0xa6/0xb0
Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020790]
[<ffffffff810130ea>] child_rip+0xa/0x20
Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020795]
[<ffffffff810786a0>] ? kthread+0x0/0xb0
Dec 19 14:23:13 Kitchen-Linux kernel: [ 6482.020799]
[<ffffffff810130e0>] ? child_rip+0x0/0x20
Dec 19 16:52:05 Kitchen-Linux kernel: imklog 4.2.0, log source =
/var/run/rsyslog/kmsg started.
Dec 19 16:52:06 Kitchen-Linux kernel: [    0.000000] Initializing
cgroup subsys cpuset
Dec 19 16:52:06 Kitchen-Linux kernel: [    0.000000] Initializing
cgroup subsys cpu