hibernation fails on vaio sz650n, Intel 965 display adapter

Hardy

SOrry, previous dmesg is from Gutsy not Hardy. This too is Gutsy.

Hi Michael,

You mentioned this is failing on Hardy as well. Would it be possible for you to capture your dmesg output when Running Hardy? Can you also look in /var/log/kern.log.0 after you have to reboot after you attempt to Hibernate. I'm just curious if any more useful error messages might be captured.

And just a small note, I've opened a task against the 'linux' package as that is the Hardy kernel source package. The "Linux" package is actually the target for upstream kernel bug reports. I know it's confusing, but hope that helps. Thanks!

I've opened a new task against the actively developed kernel and am closing the report against linux-source-2.6.22. Thanks!

From Hardy

Leann

Hardy has successfully hibernated and resumed a couple of times today, though the notebook goes through POST and GRUB before giving me a locked-screen type of login prompt (not the usual GDM one). I tried a third time and hibernation failed - no kern.log.0 on the system though, sorry. Once I had some errors echo to the screen during hibernation but they haven been repeated and related to the webcam module and iwl4965

Hi Michael,

It would seem that things are getting a bit better with the development kernel (Hardy). I'm curious if you've tested with the most recent kernel that's been published, 2.6.24-4.7. Thanks.

Hi Leann - haven't tested with that kernel yet; will it be in the daily
iso? Can have a go in the weekend, and will definitely have a go when
alpha-4 comes out at the end of the month.

Leann Ogasawara wrote:
> Hi Michael,
>
> It would seem that things are getting a bit better with the development
> kernel (Hardy). I'm curious if you've tested with the most recent
> kernel that's been published, 2.6.24-4.7. Thanks.
>
>

Hi Michael,

Sorry for the delayed response. Definitely, if you can test with Alpha 4 that would be great. It should be out within a day or two. It's kernel should be 2.6.24-5.9 I believe. As for the daily builds, I glanced at the manifest:

http://cdimage.ubuntu.com/daily-live/current/hardy-desktop-i386.manifest

and it looks like that has kernel 2.6.24-5.8 right now. Hope that helps. Thanks!

Hibernation works with Hardy alpha 4, but only with the Intel 965 display adapter. The nVidia 8400M GS still refuses to either resume from suspend or hibernate properly. dmesg from successful hibernate attached.

Hi Michael,

Care to update the title and summary of this report to specifically target your Nvidia card. As I had mentioned in your other bug report regarding Suspend issues, failure to Hibernate is hardware specific. Also, if you could attach your logs after a failure, that would be more helpful. Thanks!

HIbernate writes to disk, then reboots from POST and GRUB in Hardy alpha 5

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.

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!