Dapper panasonic Cf-Y4 hibernate and sleep don't work

[Mante]

I found this problem on my laptop a panasonic (Matsushita) CF-Y4JW8AXR, but I think that at this level Dapper still doesn't support hibernate because the kernel is not patched and the hibernate package was not installed. In Breeze the hibernate support was eccellent. At the present time with Dapper I can't do hibernate or sleep.

Hibernate:
Select hibernate from gnome - Screen goes black for few seconds and then back to gnome

Sleep:
Laptop enter correctly in sleep mode (I suppose) but when I try to go back to normal mode system freezes down. On black screen a cursor (not blinking) is displayed in the top left size of the screen but no command works.

[Carthik Sharma (carthik)]

Hi,

Thank you for reporting this bug. Is this still an issue with the latest Dapper packages installed?

[Mante (mante)]

Sorry for the delay.

Tried before, supposly goes in hibernate mode, but when trying to restore the system, the screen displays some orizzontal orange lines and the os freezes down.

[Danny Staple (danny-orionrobots)]

Hi,

I see something similar to Mante. Trying out hibernate for the first time on Dapper (installed yesterday via synaptic), I can get it to go into hibernate mode, but then upon trying to restore it I get vertical grey lines, and the OS appears to be locked up.

Thinking it may have been just the X video driver, I tried ctrl-alt-f1 through f12, and saw no change. In the end I was forced to reset.

Information on the machine:
I am using the K7 kernel, on Dapper 6.06 LTS. My graphics card is an NVidia gforce 6600 (AGP) and I am running the nonfree nvidia drivers for it.

My CPU is an AMD Sempron 3000+, the machine has 1Gb of RAM, and the main drive (mounted on /) is 80Gb (75Gb formatted) and has only 6.7Gb used. There is also a secondary 160Gb (152Gb formatted) drive mounted only under /media/hda2 - and is really only used for music.

The motherboard is an NForce 3 250 based board - the Gigabyte K8NS.

[Mante (mante)]

Doing latest ubuntu updates Kernel 2.6.15-26, Hybernate still doesn't work, but this time system doesn't try to hibernate as before and I receive a warning in the top right corner of the gnome panel reporting that an HAL problem has occurred and to follow a FAQ page to find a solution myself.

[trollord (trollenlord)]

The issue that you reported is one that should be FIXED in the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at [WWW] http://www.ubuntu.com/testing/

[trollord (trollenlord)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Mante (mante)]

Testing with Gutsy final, suspend is still buggy.
Alex

trollord wrote:
> The issue that you reported is one that should be FIXED in the
> development release - Gutsy Gibbon. It would help us greatly if you
> could test with it so we can work on getting it fixed in the actively
> developed release. You can find out more about the development release
> at [WWW] http://www.ubuntu.com/testing/
>
>

[Mante (mante)]

As request by Canonical. Actually sleep (suspend) is still buggy

[Mante (mante)]

Hibernate checked. Doesn't work too. Machine is shut down instead.
This is a regression compared to edgy.

[Mante (mante)]

Hibernate checked. Doesn't work too. Machine is shut down instead.
This is a regression compared to feisty.

[Andres Mujica (andres.mujica)]

Hi Mante, thnaks for your information and reporting back this issue.

To be more accurate with your bug report would you help us with the information i'm transcribing from https://wiki.ubuntu.com/DebuggingKernelSuspend

That link explains how to debug kernel suspend and hibernate issues as the ones you're having.

....
In order to stimulate your suspend/resume process, enter the following commands (as root):

sync; echo 1 > /sys/power/pm_trace; /etc/acpi/sleep.sh force

At this point your computer should enter the suspend state within a few seconds. Usually the power LED will slowly flash when in the suspended state. When that has happened, initiate the resume process by pressing the power button. Observe closely if the disk light comes on briefly. This indicates that resume has begun. If resume fails to complete, then press the power button until the computer turns off. Power on your computer making sure that it loads the same kernel that exhibited the resume problem. You have about 3 minutes to start this boot process before the information saved in the RTC gets corrupted.

Start a console and enter:

dmesg > dmesg.txt

You can edit this file and find line similar to these:

[ 11.323206] Magic number: 0:798:264
[ 11.323257] hash matches drivers/base/power/resume.c:46

There may well be another 'hash matches' line beyond that. If so, then you are in luck because the last one is the likely culprit. For example:

hash matches device i2c-9191

The only way to prove this is to remove the module prior to initiating suspend. Repeat as needed...

[Andres Mujica (andres.mujica)]

Also we would need this info

      uname -a > uname-a.log
      cat /proc/version_signature > version.log
     dmesg > dmesg.log
      sudo lspci -vvnn > lspci-vvnn.log

and attach those to this bug report

Thanks

[Mante (mante)]

Hello, The method below works ^^;

sync; echo 1 > /sys/power/pm_trace; /etc/acpi/sleep.sh force

still sleep and hibernate don't work with the usual method (by pressing special keys) ->
black screen after few secs.

SEAQ - Andres Mujica wrote:
> Also we would need this info
>
>
> uname -a > uname-a.log
> cat /proc/version_signature > version.log
> dmesg > dmesg.log
> sudo lspci -vvnn > lspci-vvnn.log
>
> and attach those to this bug report
>
>
> Thanks
>
>

[Andres Mujica (andres.mujica)]

Ok, sorry for the long delay in getting back here.

Can you help me with the data asked here

 https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/35557/comments/13

also have you already tested or upgraded to hardy? is the bug still present?

thanks

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Ralph Janke (txwikinger)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks.