Description of problem: dmesg/logs contain messages like these: snd-usb-audio 1-5:1.1: no suspend for driver snd-usb-audio? snd-usb-audio 1-5:1.2: no suspend for driver snd-usb-audio? Is there a problem with suspending the snd-usb-audio driver? Version-Release number of selected component (if applicable): 2.6.23.1-49.fc8 but also visible in f7 How reproducible: Always Steps to Reproduce: 1. Suspend computer 2. Resume computer 3. Examine logs Actual results: Log entries as above Expected results: No log entries Additional info:
I guess you may need to have a usb audio device connected! My notebook seems to have it built-in, perhaps the TV tuner.
Hello David, Can this one be closed now - I can't tell if your comment #1 indicates this was NOTABUG?
I haven't seen it for a few days, but I believe it is still there. Later I'll try shutting the computer down to suspend with a USB phone connected.... and in any case I'll watch for it... It looks like the messages are logged when coming out of suspend. Here's some recent log output with the -85 kernel. I'm now running the -137 kernel. [root@host15-101 ~]# egrep "Linux version|no suspend" /var/log/messages-20080127 Jan 22 12:03:39 localhost kernel: snd-usb-audio 1-5:1.1: no suspend for driver snd-usb-audio? Jan 22 12:03:39 localhost kernel: snd-usb-audio 1-5:1.2: no suspend for driver snd-usb-audio? Jan 23 07:29:20 localhost kernel: snd-usb-audio 3-1:1.0: no suspend for driver snd-usb-audio? Jan 23 07:29:20 localhost kernel: snd-usb-audio 3-1:1.1: no suspend for driver snd-usb-audio? Jan 23 07:29:20 localhost kernel: snd-usb-audio 3-1:1.2: no suspend for driver snd-usb-audio? Jan 23 07:29:20 localhost kernel: snd-usb-audio 1-5:1.1: no suspend for driver snd-usb-audio? Jan 23 07:29:20 localhost kernel: snd-usb-audio 1-5:1.2: no suspend for driver snd-usb-audio? Jan 23 10:04:44 localhost kernel: Linux version 2.6.23.9-85.fc8 (kojibuilder.phx.redhat.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Fri Dec 7 15:49:59 EST 2007 Jan 24 07:39:50 localhost kernel: snd-usb-audio 3-1:1.0: no suspend for driver snd-usb-audio? Jan 24 07:39:50 localhost kernel: snd-usb-audio 3-1:1.1: no suspend for driver snd-usb-audio? Jan 24 07:39:50 localhost kernel: snd-usb-audio 3-1:1.2: no suspend for driver snd-usb-audio? Jan 24 07:39:50 localhost kernel: snd-usb-audio 1-5:1.1: no suspend for driver snd-usb-audio? Jan 24 07:39:50 localhost kernel: snd-usb-audio 1-5:1.2: no suspend for driver snd-usb-audio? Jan 24 07:59:02 host15-102 kernel: Linux version 2.6.23.9-85.fc8 (kojibuilder.phx.redhat.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Fri Dec 7 15:49:59 EST 2007 Jan 27 07:05:10 host15-102 kernel: snd-usb-audio 1-5:1.1: no suspend for driver snd-usb-audio? Jan 27 07:05:10 host15-102 kernel: snd-usb-audio 1-5:1.2: no suspend for driver snd-usb-audio? Jan 27 12:17:33 host15-102 kernel: snd-usb-audio 1-5:1.1: no suspend for driver snd-usb-audio? Jan 27 12:17:33 host15-102 kernel: snd-usb-audio 1-5:1.2: no suspend for driver snd-usb-audio?
If it re-occurs can you attach as individual text/plain attachments: lsusb > lsusb.out # lspci -vvxxx > lspci.out dmesg > dmesg.out lsmod > lsmod.out
Problem happened this morning when I brought my computer out of suspend. Attaching files as requested.
Created attachment 294942 [details] lsmod output
Created attachment 294943 [details] lspci output
Created attachment 294946 [details] lsusb output
Created attachment 294947 [details] dmesg output
I admit that the kernel is tainted by vmware loadable modules, but I believe it to be completely unrelated to the usb audio issue I see. If need be I can boot the machine without those modules loaded.
Yeah, we generally need people to do that in the first instance as you're probably aware. If you can do so and re-test that would be good. You're not just getting it for audio either: snd-usb-audio 1-5:1.1: no resume for driver snd-usb-audio? snd-usb-audio 1-5:1.2: no resume for driver snd-usb-audio? usbfs 1-1.2:1.0: no resume for driver usbfs?
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as INSUFFICIENT_DATA.