Maverick hangs

[jmlaniel]

Can you post the link to the launchpad bug?

[turbolad]

Can you post the link to the launchpad bug?

Here: https://bugs.launchpad.net/ubuntu/+bug/660595

[Boboms]

They will definitly help, this is matter of time. Thank you for bug report, give me link, I'll aslo comment bug.

[turbolad]

For everyone with this same problem: please leave your comments on the bug report via the link in my previous post. If you haven't already registered for Ubuntu's Launchpad, it's quick to create a username and password.

Hopefully somebody will create a fix we can all receive via the updates.

[Mystic-Mirage]

Bug report on launchpad.

That is the link in my message...

[turbolad]

The link to launchpad in my message can be clicked on. Please report the standby problems on Launchpad too.

[jmlaniel]

Here is the official link to the official bug :

https://bugs.launchpad.net/ubuntu/+sour ... bug/640100

The bug has been recognized officially but has not been treated yet. A lot is going on right now and it might help if you join yourself as affected by the bug (opening an account is quite fast).

[turbolad]

It's a big problem and no idea who can fix it and when!!

[laforge]

As you can read on the official bug, there is a workaround for this problem, you can install this kernel that permit to work with the suspend:
http://kernel.ubuntu.com/~kernel-ppa/ma ... -maverick/

Donwload this files:
http://kernel.ubuntu.com/~kernel-ppa/ma ... 5_i386.deb

http://kernel.ubuntu.com/~kernel-ppa/ma ... 05_all.deb

http://kernel.ubuntu.com/~kernel-ppa/ma ... 5_i386.deb

After downloaded open a shell and run this command in the same folder you have those file:

dpkg -i linux-*

During the install, if you have installed the samsung backlight , you'll see the compilation of the module for this kernel, so you can get suspend and backlight working fine, using this kernel. Remember to use this kernel on next reboot.

[disposed]

As you can read on the official bug, there is a workaround for this problem, you can install this kernel that permit to work with the suspend:
http://kernel.ubuntu.com/~kernel-ppa/ma ... -maverick/

Donwload this files:
http://kernel.ubuntu.com/~kernel-ppa/ma ... 5_i386.deb

http://kernel.ubuntu.com/~kernel-ppa/ma ... 05_all.deb

http://kernel.ubuntu.com/~kernel-ppa/ma ... 5_i386.deb

After downloaded open a shell and run this command in the same folder you have those file:

dpkg -i linux-*

During the install, if you have installed the samsung backlight , you'll see the compilation of the module for this kernel, so you can get suspend and backlight working fine, using this kernel. Remember to use this kernel on next reboot.

Worked fine except it cant build the kernel modules without the source.

Used this instead.

http://kernel.ubuntu.com/~kernel-ppa/ma ... -maverick/

[svlad cjelli]

Same here... installed the mainline-kernel 2.6.36 and thesuspend-problem was gone.
But now the backlight control does not work. I think only vorias kernel would work, and that is the one with the kernel bug, isnt it?

couldn't someone fix this in the vorias kernel so that we have backlight control and fn-keys and thats stuff?

[DarrellKavanagh]

Workaround: adding intel_idle.max_cstate=0 to kernel boot parameters works for me (N210 Plus) with the latest Maverick Kernel (2.6.35-24-generic) and the latest Voria kernel 2.6.35-23.

See launchpad bug linked above - thanks to Daniel Schindler.

[ppmt]

I can confirm that so far setting

intel_max.idle_cstate=0 solves the suspend issue.


I have tried to suspend it several time and it always came back. Even wireless comes back

This is great!

[zobar]

The kernel bug for this is #21952. I believe this bug is nearing resolution, but the programmer it's assigned to needs to know whether the Voria kernel contains his patch for kernel bug #21032 System hangs on Boot on Intel ATOM (samsung n510 @nynet).

Code: Select all

$ uname -a
Linux tinytronix 2.6.35-24-generic #43~ppa1~loms~maverick-Ubuntu SMP Fri Dec 24 18:15:40 UTC 2010 i686 GNU/Linux

- dpk

[nanders]

I can confirm that so far setting
intel_max.idle_cstate=0 solves the suspend issue.

Same here (N210 with 10.10/2.6.23-25 ), however I think it's slightly mistyped.

You should append:
"intel_idle.max_cstate=0"

to the default boot parameters (/etc/default/grub). On my machine I can use both suspend and hibernate again. Great!

see also:

Here is the official link to the official bug :
https://bugs.launchpad.net/ubuntu/+sour ... bug/640100

post #115