Bug 62691 - no reset_resume for driver snd-usb-audio for logitech headset H600
Summary: no reset_resume for driver snd-usb-audio for logitech headset H600
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Greg Kroah-Hartman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-07 19:30 UTC by Bernhard B.A.
Modified: 2013-10-08 16:59 UTC (History)
0 users

See Also:
Kernel Version: 3.11.x
Subsystem:
Regression: No
Bisected commit-id:


Attachments
lsusb -vv (8.52 KB, text/plain)
2013-10-07 19:30 UTC, Bernhard B.A.
Details

Description Bernhard B.A. 2013-10-07 19:30:45 UTC
Created attachment 110391 [details]
lsusb -vv

Hello!

I use the Logitech Wireless Headset H600, which is connected with USB 2.0:
Bus 001 Device 008: ID 046d:0a29 Logitech, Inc. H600 [Wireless Headset]

In syslog the messages "no reset_resume for driver snd-usb-audio?" occur and the device is removed and is reset. 
So in KDE at kmix the device is removed as main device and the master channel switching for the volume (increase, decrease) is set to a default device (onboard audio). 
So I have to set the master channel again at every resume from hibernate/standby.
I suspect here the "no reset_resume"-problem as culprit.

I use the headset on a usb 2.0 hub and without hub => no difference.

Thank you for your help!

Best regards, Bernhard


syslog:
[24788.193800] usb 2-1: reset high-speed USB device number 2 using ehci-pci
[24788.249611] firewire_core 0000:0c:03.0: rediscovered device fw0
[24788.397420] usb 1-1.4: reset high-speed USB device number 3 using ehci-pci
[24788.792794] usb 2-1.2: reset low-speed USB device number 3 using ehci-pci
[24789.144536] usb 1-1.4.3: reset high-speed USB device number 4 using ehci-pci
[24789.515956] usb 1-1.4.3.4: reset full-speed USB device number 6 using ehci-pci
[24789.679749] usb 1-1.4.3.3: reset full-speed USB device number 5 using ehci-pci
[24789.841988] snd-usb-audio 1-1.4.3.3:1.0: no reset_resume for driver snd-usb-audio?
[24789.841991] snd-usb-audio 1-1.4.3.3:1.1: no reset_resume for driver snd-usb-audio?
[24789.841993] snd-usb-audio 1-1.4.3.3:1.2: no reset_resume for driver snd-usb-audio?
[24789.845400] PM: restore of devices complete after 2233.681 msecs
[24789.897878] Restarting tasks ... done.
[24790.806793] r8169 0000:05:00.0 eth0: link down
[24790.806807] r8169 0000:05:00.0 eth0: link down
[24790.806826] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[24792.423120] r8169 0000:05:00.0 eth0: link up
[24792.423131] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[24844.385724] usb 1-1.4.3.3: USB disconnect, device number 5
[24845.095386] usb 1-1.4.3.3: new full-speed USB device number 8 using ehci-pci
[24845.536823] usb 1-1.4.3.3: New USB device found, idVendor=046d, idProduct=0a29
[24845.536829] usb 1-1.4.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[24845.536834] usb 1-1.4.3.3: Product: Logitech Wireless Headset
[24845.536837] usb 1-1.4.3.3: Manufacturer: Logitech
[24845.536840] usb 1-1.4.3.3: SerialNumber: 000d44b20870
[24845.621934] input: Logitech Logitech Wireless Headset as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.3/1-1.4.3.3/1-1.4.3.3:1.3/input/input18
[24845.622719] hid-generic 0003:046D:0A29.0007: input,hiddev0,hidraw1: USB HID v1.11 Device [Logitech Logitech Wireless Headset] on usb-0000:00:1a.0-1.4.3.3/input3

Xorg.log:
[dix] Logitech Logitech Wireless Headset: unable to find touch point 0
Comment 1 Greg Kroah-Hartman 2013-10-07 20:16:17 UTC
On Mon, Oct 07, 2013 at 07:30:45PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=62691
> 
>             Bug ID: 62691
>            Summary: no reset_resume for driver snd-usb-audio for logitech
>                     headset H600

Please send this to the linux-usb@vger.kernel.org mailing list
Comment 2 Bernhard B.A. 2013-10-08 16:59:48 UTC
> Please send this to the linux-usb@vger.kernel.org mailing list

Done!

Note You need to log in before you can comment on or make changes to this bug.