suspend/resume broken on hp nc 6320

[Erik I]

Description: Ubuntu 8.04
Release: 8.04

Suspend/resume worked fine on 2.6.24-13, was broken on 2.6.24-14, worked again on 2.6.24-15 and, for me at least, is broken again on 2.6.24-16.

[Leann Ogasawara (leannogasawara)]

Hi Erik,

Per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.

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

It would also be helpful to capture your dmesg output after an attempted suspend/resume cycle as outlined here: https://wiki.ubuntu.com/DebuggingKernelSuspend . For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

[spencer davies (bogwelsh)]

I have the same problem as Erik. I can confirm both suspend and hibernate worked ok in 2.6.24-15 and has stopped working in 2.6.24-16 (since installing 8.04). The problem appears on the suspend/hibernate side rather than during resume. When doing suspend the system goes to complete shutdown; when doing hibernate it streams out a usb error message; hitting ctrl/z sends it to complete shutdown.

version.log, dmesg.log and lspci-vvnn.log attached

Regards,

Spencer.
reports a

[spencer davies (bogwelsh)]

reports a

[Jakob Petsovits (jpetso)]

Doesn't work on my nc6320 either. I guess with 3 affected people it should be ok to mark this bug as "confirmed".

[Jakob Petsovits (jpetso)]

Doesn't work on my nc6320 either. I guess with 3 affected people it should be ok to mark this bug as "confirmed", so I changed the status. Thanks for retrieving the log files, spencer - now I don't have to do it myself :P

[Festr (festr)]

I can confirm this bug on my nc6320

[Erik I (erik-itland)]

Still broken with 2.6.24-19-generic

Going to upload new version.log, dmesg.log and lspci-vvnn.log

[Leann Ogasawara (leannogasawara)]

Hi Erik,

As you've confirmed, it unfortunately looks like this is still not resolved with the latest Hardy kernel. Just curious if you'd be willing to test the upcoming Intrepid Ibex 8.10 release which is actively being developed. You should be able to test Suspend via a LiveCD - http://www.ubuntu.com/testing. If you are able to test, please let us know your results. Thanks.

[Erik I (erik-itland)]

I've just tested Intrepid Ibex Alpha 3 on my laptop. I suspended it
twice, and it resumed both times. Hardy fails every time, as far as
I've tested.

2008/8/8, Leann Ogasawara <email address hidden>:
> Hi Erik,
>
> As you've confirmed, it unfortunately looks like this is still not
> resolved with the latest Hardy kernel. Just curious if you'd be willing
> to test the upcoming Intrepid Ibex 8.10 release which is actively being
> developed. You should be able to test Suspend via a LiveCD -
> http://www.ubuntu.com/testing. If you are able to test, please let us
> know your results. Thanks.
>
> --
> suspend/resume broken on hp nc 6320
> https://bugs.launchpad.net/bugs/219657
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Leann Ogasawara (leannogasawara)]

Hi Erik,

Thanks for testing the Intrepid Alpha release. From you comments it sounds promising. I'm going to tentatively mark this Fix Release for Intrepid.

Now the bigger issue is trying to narrow down the patch(es) which resolved this in Intrepid and see if they will qualify at a Stable Release Update for Hardy. That's a rather difficult task as the Hardy kernel is a 2.6.24 kernel and the Intrepid kernel is a 2.6.26 kernel. The amount of patches that went into between the two versions is quite large. How comfortable would you be performing a git bisect ? It will require some knowledge of building the kernel. This is obviously something we do not expect bug reporters to know how to do and it is completely at your own comfort level if you are willing to give it a try. The git bisect basically helps narrow down the exact patch that can cause a regression or resolve a bug. The only reason I ask for your help with this is because this issue really is hardware specific and since you have the hardware to reproduce the issue, you're likely the best candidate to help with performing the git bisect. But again, this is completely your choice. More information regarding how to perform a git bisect can be found here:

http://www.kernel.org/doc/local/git-quick.html#bisect

The only small change is that you'll have to switch the meanings of "Good" and "Bad" since you are trying to isolate the patch which resolved the bug, not caused the regression.

Information regarding the Ubuntu git kernel tree for Intrepid can be found at:

https://wiki.ubuntu.com/KernelGitGuide

And finally information about building the Ubuntu kernel is here:

https://help.ubuntu.com/community/Kernel/Compile

Again I completely understand if this is a bit overwhelming and not something you'd be willing to do. But given the limited kernel resources we have, we really do appreciate all the help we can get from community members like yourself. Thanks.

[Erik I (erik-itland)]

Hi again Leann

I'll see if I can find time to investigate it further. However, I've barely
compiled a kernel before, so don't expect too much : )

The people at the ubuntu-users list advised me to try to find the
differences between the kernel versions the last days before the release of
Hardy (because it was working, broken, fixed it, and then broken again, so
it should be possible to find some similarties between the broken ones and
some differences between the broken and the good ones.) Could that be an
easier solution?

Regards,
Erik

[Leann Ogasawara (leannogasawara)]

Hi Erik,

Narrowing down the specific versions which worked and then which broke could be helpful. That at least helps narrow down the possibilities for patches. Ulitimately though we will still need to isolate the exact patch.

[linuxrules (linuxrules)]

out of all things I thought of live booting from the same CD I used to install ubuntu and 10 bugs I had with ubuntu on hard disk did not exist in the live-boot session. The 10 bugs that did not exist:
1)screen refresh not consistent, SDL suffers
2) usplash quits
3)suspend/hibernate fail
4)buttons missing
5)screen-saver freeze computer
6)ubuntu randomly say im in low graphics mode
7)progress bar on boot gets stuck
8)unable to move window
9)computer freezes some times when I try to move file to trash icon
10)crash on resume
By the looks of it this might be a installer problem
The installer I used disk containing wubi
but the installed ubuntu has bugs
by the way should I attach a zip containing the CD contents

[Julian Wiedmann (jwiedmann)]

This release has reached end-of-life [0].

[0] https://wiki.ubuntu.com/Releases