Jaunty - Error messages in (kern.log) during resume

[JByteCoder]

Binary package hint: linux-image-2.6.28-11-generic

This bug dose not affect my work with the system - i report this only because i i thnk it might help make the suspend under linux more reliable.

I've experinenced this using latest Jaunty

somtimes usually after few suspends, durring resume i get information like Device 1-3 resume failed and something about USB (i've attached that kern.log - the interesting meseges are from 2009-04-04 02-20-09)

There is one more thing not neccesarry related to this bug .

The more suspends my Jaunty was in the slower it works after. i've also observed that sometimes it uses very much SWAP when stil haveing lots of RAM free example;

i had that situation that 150 MB RAM was used (of 1GB) and 1GB (of 1GB) of SWAP was used, and system worked teribly slow

what other information should i provide ?

[JByteCoder (jbytecoder)]

System forgot to add Kern.log

[Pete Graner (pgraner)]

This happens on my Dell M1330.

Adding regression-potential and assigning apw, also subscribing ogasawara.

[Steve Langasek (vorlon)]

I'm puzzled by this bug's description; what exactly is the bug that's being tracked as a target for the Ubuntu release? I don't find any references to device resume failures in the attached kernel log, nor log entries with the specified timestamp; and there are plenty of USB messages but it's not clear to me which one is believed to be the problem?

[JByteCoder (jbytecoder)]

Apr 4 22:50:43 uriel-laptop kernel: [63361.153242] PM: Device 3-1 failed to resume: error -19
Apr 4 22:50:43 uriel-laptop kernel: [63361.153580] PM: resume devices took 4.880 seconds
Apr 4 22:50:43 uriel-laptop kernel: [63361.153788] PM: Finishing wakeup.

i'm sorry that i passed wrong timestamp

i'm worried about the part above
after time i can say it happens very rarley,'ve noticed it happens only with hibernate-ram program

is the above a problem or is it kind of normal thing

[Steve Langasek (vorlon)]

As far as I know, having USB devices not resume isn't a major issue unless the device in question is a mounted USB disk, but you didn't mention that this was the case? Also, a device not resuming could simply mean the device was attached at suspend time, and was unplugged prior to resume.

I don't think the log message alone is anything to worry about unless it corresponds to a problem using your hardware after resume.

[Steve Langasek (vorlon)]

deferring to jaunty-updates; but I'm still not clear why this is marked as a regression.

[Andy Whitcroft (apw)]

@vorlon -- I believe that this was reported because these messages are visible on the terminal after the screen comes back on and before X is restored. It was more of a prettyness issue than a bug per-see.

@pgraner, @jbytecoder -- can you confirm if these messages are still visible during resume on these systems.

[IanW (f-launchpad-drianwalker-com)]

I also get this issue. E.g., from kern.log:

May 27 21:15:14 MacKubuntu kernel: [ 3003.296119] usb 3-1: reset full speed USB device using uhci_hcd and address 4
May 27 21:15:14 MacKubuntu kernel: [ 3003.360168] pm_op(): usb_dev_resume+0x0/0x10 returns -19
May 27 21:15:14 MacKubuntu kernel: [ 3003.360171] PM: Device 3-1 failed to resume: error -19
May 27 21:15:14 MacKubuntu kernel: [ 3003.360410] PM: resume devices took 4.260 seconds
May 27 21:15:14 MacKubuntu kernel: [ 3003.361146] PM: Finishing wakeup.
May 27 21:15:14 MacKubuntu kernel: [ 3003.361147] Restarting tasks ... done.
May 27 21:15:14 MacKubuntu kernel: [ 3003.688140] usb 3-1: USB disconnect, address 4
May 27 21:15:14 MacKubuntu kernel: [ 3003.928109] usb 3-1: new full speed USB device using uhci_hcd and address 5
May 27 21:15:14 MacKubuntu kernel: [ 3004.113609] usb 3-1: configuration #1 chosen from 1 choice

If I do lsusb -v I see that usb 3-1 is:

Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 0 Full speed (or root) hub
  bMaxPacketSize0 64
  idVendor 0x1d6b Linux Foundation
  idProduct 0x0001 1.1 root hub
  bcdDevice 2.06
  iManufacturer 3
  iProduct 2
  iSerial 1
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 25
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xe0
      Self Powered
      Remote Wakeup
    MaxPower 0mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4 ...