Feisty: resume from S3: minor USB glitches

[Hoffmann]

After resuming from S3 on my Turion based notebook, I have tons of the following messages in dmesg output:

during suspend:

 hub 4-0:1.0: suspend
 usb usb4: suspend, may wakeup
 usbdev3.1_ep81: PM: suspend 0->2, parent 3-0:1.0 already 2
 hub 3-0:1.0: PM: suspend 2-->2
 hub 3-0:1.0: PM: suspend 2->2, parent usb3 already 2
 usbdev3.1_ep00: PM: suspend 0->2, parent usb3 already 2
 usb usb3: PM: suspend 2-->2
 usbdev2.1_ep81: PM: suspend 0->2, parent 2-0:1.0 already 2
etc.

and during resume:

 usb 4-2: resuming
 usbdev4.2_ep00: PM: resume from 0, parent 4-2 still 2
etc.

This is on a Via based chipset. This looks like a wrong sequence? Shouldn't the children suspend before the parents? And resumed vice versa?

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

[Hoffmann (bubble-fish)]

Here's the output of uname -a:

Linux bla-laptop 2.6.20-15-generic #2 SMP Sun Apr 15 06:17:24 UTC 2007 x86_64 GNU/Linux

[Hoffmann (bubble-fish)]

Be aware: This is a dmesg of _two_ consecutive suspend/resume cycles (S3 of course). Interestingly there are new errors due to the second run. -> Perhaps another bug report?

[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.

[Hoffmann (bubble-fish)]

So I installed the linux-image-2.6.27-2-generic kernel onto my hardy machine:

Now this bug is gone!

In "pure" Hardy (i.e. 2.6.24-* kernels) this bug is still valid though.... Hence I keep this open.

off-topic: Hurray: cpuidle is working finally with 2.6.27. (as opposed to Hardy)

[Leann Ogasawara (leannogasawara)]

Thanks Hoffmann. I'm marking this Fix Released for Intrepid. Based on current SRU policy - http://wiki.ubuntu.com/StableReleaseUpdates it's not likely a fix will be backported to Hardy. Thanks.