resume hangs

Also, I did the instructions listed on:

https://wiki.ubuntu.com/DebuggingKernelSuspend

and got this from the dmesg:
[ 0.270364] Magic number: 0:626:449

but not the:
[ 11.323257] hash matches drivers/base/power/resume.c:46
 or
hash matches device i2c-9191

in the dmesg.

Thanks,
Tino

Hi Tino,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Hi Jeremy,

     I have tested with latest kernel:

Linux wintermute 2.6.34-996-generic #201006021548 SMP Wed Jun 2 15:55:17 UTC 2010 i686 GNU/Linux

It is still hanging my kernel on resume. Is there any logs or other files that you would like to see. Also, I went ahead and removed the 'needs-upstream testing' tag per your request.

Thanks in advance,
Tino

Anything else that I can do on this end (besides wait)? -Tino

On Tue, Jun 8, 2010 at 10:28 AM, Jeremy Foshee
<email address hidden>wrote:

> ** Changed in: linux (Ubuntu)
> Status: Incomplete => Triaged
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Tags added: kernel-power
> ** Tags removed: needs-upstream-testing
>
> --
> resume hangs kernel with nouveau drivers
> https://bugs.launchpad.net/bugs/590516
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Triaged
>
> Bug description:
> I switched from the nv to nouveau to stop the flicking of X and the
> choppi-ness of youtube/hulu/etc. I am very satisfied with the nouveau
> driver, except I can suspend or hibernate. I found this in my
> /var/log/kern.log right before it hung the kernel.
>
> Jun 6 09:40:17 wintermute kernel: [ 1626.352132] PM: resume of
> drv:yenta_cardbus dev:0000:02:0b.0 complete after 195.913 msecs
> Jun 6 09:40:17 wintermute kernel: [ 1626.355355] serial 00:09: activated
> Jun 6 09:40:17 wintermute kernel: [ 1626.390655] sd 0:0:0:0: [sda]
> Starting disk
> Jun 6 09:40:17 wintermute kernel: [ 1626.416084] PM: resume of devices
> complete after 2886.102 msecs
> Jun 6 09:40:17 wintermute kernel: [ 1626.416192] PM: resume devices took
> 2.888 seconds
> Jun 6 09:40:17 wintermute kernel: [ 1626.416223] PM: Finishing wakeup.
> Jun 6 09:40:17 wintermute kernel: [ 1626.416225] Restarting tasks ...
> done.
> Jun 6 09:40:17 wintermute kernel: [ 1626.650970] ADDRCONF(NETDEV_UP):
> eth1: link is not ready
> Jun 6 09:40:17 wintermute kernel: [ 1626.674406] ADDRCONF(NETDEV_UP):
> eth0: link is not ready
> Jun 6 09:40:17 wintermute kernel: [ 1626.817872] [drm] nouveau
> 0000:01:00.0: PFIFO_INTR 0x00010000 - Ch 0
>
> .... repeated for 101 times I guess ......
>
> Jun 6 09:40:17 wintermute kernel: [ 1626.818312] [drm] nouveau
> 0000:01:00.0: PFIFO_INTR 0x00010000 - Ch 0
> Jun 6 09:40:17 wintermute kernel: [ 1626.818316] [drm] nouveau
> 0000:01:00.0: PFIFO_INTR 0x00010000 - Ch 0
> Jun 6 09:40:17 wintermute kernel: [ 1626.818320] [drm] nouveau
> 0000:01:00.0: PFIFO still angry after 101 spins, halt
> Jun 6 09:40:18 wintermute kernel: [ 1627.350680] input: PS/2 Mouse as
> /devices/platform/i8042/serio1/input/input8
> Jun 6 09:40:18 wintermute kernel: [ 1627.375146] input: AlpsPS/2 ALPS
> GlidePoint as /devices/platform/i8042/serio1/input/input9
> Jun 6 09:40:18 wintermute kernel: [ 1627.594732] ADDRCONF(NETDEV_CHANGE):
> eth1: link becomes ready
> Dec 9 10:00:00 wintermute kernel: imklog 4.2.0, log source = /proc/kmsg
> started.
> Dec 9 10:00:00 wintermute kernel: [ 0.000000] Initializing cgroup
> subsys cpuset
> Dec 9 10:00:00 wintermute kernel: [ 0.000000] Initializing cgroup
> subsys cpu
>
> And then I need to do a hard boot. Any thing that I can provide for the
> Ubuntu team, just ask. Thanks -Tino
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.04
> Package: linux-image-2.6.32-22-generic 2.6.32-22.36
> Regression: Yes
> Reproducible: Yes
> ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
> Uname: Linux 2.6.32-22-generic i686
>...

Hi I've been having suspend/resume issues with cgroups and this bug came up in a search I believe your problem is caused by https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/693594

Do you have a multicore/hyperthreaded machine?
If so could you try the following
* Open a few root prompts
* check mount for where your cgroups fs is (mine is /sys/fs/cgroup/cpu/ on previous versions of ubuntu it may be elsewhere)
* In one try turning your 2nd processor off and on a few types ( e.g echo 0 > /sys/devices/system/cpu/cpu1/online ).
* If that locks up use a second prompt to run (echo 950000 > /sys/fs/cgroup/cpu/sysdefault/cpu.rt_runtime_us ) if this unlocks up the processor shutdown, a suspend/resume should now work.
* If suspend/resume works after putting a value in /sys/fs/cgroup/cpu/sysdefault/cpu.rt_runtime_us please mark this bug a duplicate of 693594 and look there for permanent fixes

Hi,

nouveau is known not to be quite buggy with ACPI S3 state (Suspend to RAM) resume.
From my own experience, this is what it looks like,

RIVA TNT2 M64 (AGP) - freeze
GeForce 2 MX (AGP) - freeze
GeForce 4 MX (AGP) - OS is running, but screen is blank. If one enters the password carefully, you will get back to the OS.
GeForce FX 5200 (AGP) - Works
GeForce 6, 7, 8, and 9 series (PCI Express): Mostly don't work, use NVIDIA written device driver instead.

The chipset used against most of the time doesn't matter too much (i.e., The problem occurs with Intel, NVIDIA, SiS, and VIA.).
Are there any plans to ever fix this problem?

Regards,

fpgahardwareengineer

Hi,

Disregard the previous message.
I posted before I proofread it.

Regards,

fpgahardwareengineer

Hi,

nouveau is known to be quite buggy with ACPI S3 state (Suspend to RAM) resume.
From my own experience, this is what it looks like,

RIVA TNT2 M64 (AGP) - freeze
GeForce 2 MX (AGP) - freeze
GeForce 4 MX (AGP) - OS is running, but screen remains blank. If one enters the password carefully, you will get back to the OS.
GeForce FX 5200 (AGP) - Works fine
GeForce 7600 GS (AGP) - Works with Intel 850E chipset when I tested it.
Various GeForce 6, 7, 8, and 9 series (PCI Express): Mostly don't work regardless of the chipset used, use NVIDIA written device driver instead (ACPI S3 resume works fine with NVIDIA written device driver.).

The chipset used against most of the time doesn't matter too much (i.e., The problem occurs with many, many Intel, NVIDIA, SiS, and VIA chipsets.).
Are there any plans to ever fix this problem?

Regards,

fpgahardwareengineer

Tino D, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.7-rc1-quantal

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]