Breezy P1, Thinkpad 600- Suspend breaks USB

[S.W.B.]

Hello,

I'd just like to mention a long-standing bug (regression) in Ubuntu's kernels
which still persists with the 2.6.12 kernel that shipped with Breezy Preview.

I have an IBM Thinkpad 600 which is currently running Hoary. When I upgraded
from Warty-->Hoary (fresh install) I started experiencing problems with my USB
mouse and USB camera not working after resuming from a suspend-to-ram. I have
verified that this a change somewhere in the kernel caused this problem, because
when I install the old 2.6.8 kernel from Warty on top of Hoary, USB works fine
with suspend-to-ram. It broke possibly with 2.6.9 and surely with 2.6.10.

This bug concerns the 2.6.12 kernel shipped with the Breezy Preview CD.
Basically, it behaves exactly the same as the 2.6.10 kernel. I am unable to
give good error messages at the moment because upgrading the libc seems to have
broken all 3 of the terminals I have installed. I am sure that this is a
regression in the kernel, and not in the APM or hotplug scripts (if there were
any changes) because as I said, Warty's kernel fixes the issue on a fresh Hoary
system, with no changes to any scripts. I'm not ready to upgrade to a full
Breezy system yet, but I hope this bug report on the Breezy kernel only will be
helpful.

Please note the old report I made on this for Hoary (also a Preview version):
http://bugzilla.ubuntu.com/show_bug.cgi?id=8565

Also please note a forum posting I made that has some more error messages.
http://ubuntuforums.org/showthread.php?t=40867

This bug does not exist with any kernels I've tried as new as 2.6.11 coming from
Mandrake.

Thanks a lot!

[Fabio Massimo Di Nitto (fabbione)]

iirc the usb drivers need to be handled properly by acpi-support.

[S.W.B. (sb73542)]

I neglected to mention that this old Thinkpad doesn't work well with ACPI. I
boot with the options "apm=on acpi=off". Thanks!

[Matt Zimmerman (mdz)]

Have you tried re-enabling ACPI with the newer kernel?

[S.W.B. (sb73542)]

OK, I just booted w/ "apm=off acpi=force noapic nolapic" and it totally ignores
the suspend key (Fn+F4). ACPI is notoriously broken on these machines. APM
should be fine, though. I have no special affinity for either method, whatever
is easiest so as to achieve suspend to RAM with working USB.

[S.W.B. (sb73542)]

Created an attachment (id=4136)
contents of /proc/acpi when enabled

[S.W.B. (sb73542)]

Created an attachment (id=4137)
dmesg, lspnp, lspci, w/ ACPI or APM

[S.W.B. (sb73542)]

I'm finally attaching some system info, dmesg's, and the contents of /proc/acpi
when I have acpi enabled. ACPI is improved over the older releases in that my
battery monitor works with it, but the USB mouse is _extremely_ jerky when I
have ACPI on. 2.6.12 w/ APM does not give me this problem. Anyway, please see
the attachments. Thanks!

[S.W.B. (sb73542)]

Hello, is there anything I can do to facilitate getting this bug fixed? Thanks!

[Mike Dahlgren (dahlgren)]

Hi,

   I noticed that this bug is currently over two years old, is this still an issue with a currently supported version of Ubuntu?

   Thanks,
       ~Mike

[Aaron Clark (aaronwclark)]

This bug still exists - I am running Fiesty with all updates on my A31 Thinkpad and builtin USB is disabled after resuming from suspend.

[Aaron Clark (aaronwclark)]

           To clarify my last comment - USB after suspend worked up until about 2.6.10 or 11. The kernel update after that broke it again and it is still broken today. The built-in USB ports are 1.1 - I have a PC Card with 2.0 ports that does work after suspend.

            I intend to upgrade to Gutsy as soon as I get a chance and will be interested to see if this problem persists.

[mmanzato (michele-manzato)]

I'm on Gutsy now and this same problem is still there. I've got an ASUS W3Z. Internal mousepad works fine after resume, USB mouse don't. Haven't tried with other USB devices.

Of course, suspend wouldn't work at all if I used fglrx for my damned Radeon Xpress 200M, but that's another story...

Thanks all
Michele

[seisen1 (seisen-deactivatedaccount-deactivatedaccount)]

Can you please test this on the latest release of Ubuntu, Hardy Heron so we can tell if it still exists in the latest kerenl?

[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 linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. 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