Bug 42906

Summary: firmware for dvb adapter
Product: Drivers Reporter: Sven Köhler (sven.koehler)
Component: OtherAssignee: drivers_other
Status: NEW ---    
Severity: normal    
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 3.2.9 Subsystem:
Regression: No Bisected commit-id:

Description Sven Köhler 2012-03-11 19:28:57 UTC
During wakeup from suspend to ram, the kernel tries to load the firmware for my dvb usb adapter but fails. The adapter was plugged in at suspend and still is plugged during wakeup. I assume the root file system is not accessible again, so loading the firmware simply happens too early and needs to be deferred to a later point in time. No such problems exist when pluggin in the USB device at a later point in time.


[53380.096429] dvb-usb: found a 'Terratec Cinergy T USB XXS (HD)/ T3' in cold state, will try to load a firmware
[53380.096434] ------------[ cut here ]------------
[53380.096442] WARNING: at drivers/base/firmware_class.c:537 _request_firmware+0x3d2/0x3f0()
[53380.096445] Hardware name: Latitude E6410
[53380.096447] Modules linked in: ir_lirc_codec lirc_dev ir_mce_kbd_decoder ir_sony_decoder ir_jvc_decoder ir_rc6_decoder dvb_usb_dib0700 dib7000p dib0090 dib7000m dib0070 dvb_usb dib8000 mt2266 tuner_xc2028 dib3000mc mxl5007t xc5000 s5h1411 mt2060 lgdt3305 dvb_core ir_rc5_decoder ir_nec_decoder rc_core xc4000 dibx000_common aesni_intel cryptd aes_x86_64 aes_generic coretemp ipv6 fuse microcode vboxnetadp(O) vboxnetflt(O) vboxdrv(O) kvm_intel kvm nvidia(P) snd_hda_codec_hdmi arc4 snd_hda_codec_idt snd_hda_intel snd_hda_codec iwlwifi uvcvideo snd_hwdep snd_pcm snd_timer snd soundcore sdhci_pci sdhci videodev firewire_ohci firewire_core sr_mod mmc_core cdrom cdc_wdm btusb bluetooth mac80211 cfg80211 rtc_cmos v4l2_compat_ioctl32 i2c_i801 usbhid i2c_core cdc_acm hid crc_itu_t e1000e snd_page_alloc psmouse evdev sg
[53380.096527] Pid: 2027, comm: pm-suspend Tainted: P           O 3.2.9 #12
[53380.096530] Call Trace:
[53380.096538]  [<ffffffff8103d29b>] ? warn_slowpath_common+0x7b/0xc0
[53380.096542]  [<ffffffff81267972>] ? _request_firmware+0x3d2/0x3f0
[53380.096549]  [<ffffffffa0e512c7>] ? dvb_usb_download_firmware+0x37/0xf0 [dvb_usb]
[53380.096554]  [<ffffffffa0e51ab4>] ? dvb_usb_device_init+0x594/0x6b0 [dvb_usb]
[53380.096561]  [<ffffffff811488e9>] ? sysfs_addrm_finish+0x29/0xc0
[53380.096566]  [<ffffffffa0e7b319>] ? dib0700_probe+0x69/0xf0 [dvb_usb_dib0700]
[53380.096571]  [<ffffffff812a0bee>] ? usb_probe_interface+0x10e/0x210
[53380.096580]  [<ffffffff8125c136>] ? driver_probe_device+0x96/0x1b0
[53380.096582]  [<ffffffff8125c2f0>] ? __driver_attach+0xa0/0xa0
[53380.096584]  [<ffffffff8125ae6c>] ? bus_for_each_drv+0x5c/0x90
[53380.096586]  [<ffffffff8125bfdf>] ? device_attach+0x9f/0xc0
[53380.096587]  [<ffffffff812a0860>] ? usb_rebind_intf+0x40/0x60
[53380.096589]  [<ffffffff812a090f>] ? do_unbind_rebind.clone.11+0x6f/0xa0
[53380.096590]  [<ffffffff812a09b0>] ? usb_resume+0x70/0xc0
[53380.096593]  [<ffffffff81293aeb>] ? usb_dev_complete+0xb/0x10
[53380.096596]  [<ffffffff81262f56>] ? dpm_complete+0x46/0x180
[53380.096600]  [<ffffffff81074d7b>] ? suspend_devices_and_enter+0x11b/0x240
[53380.096602]  [<ffffffff81075007>] ? enter_state+0x167/0x190
[53380.096604]  [<ffffffff81073e0f>] ? state_store+0xaf/0x160
[53380.096606]  [<ffffffff81147242>] ? sysfs_write_file+0xd2/0x160
[53380.096609]  [<ffffffff810e4f76>] ? vfs_write+0xc6/0x170
[53380.096611]  [<ffffffff810e525e>] ? sys_write+0x4e/0x90
[53380.096616]  [<ffffffff8138dc6f>] ? page_fault+0x1f/0x30
[53380.096618]  [<ffffffff8138e07b>] ? system_call_fastpath+0x16/0x1b
[53380.096619] ---[ end trace 1d96f9ff0800b9de ]---
[53380.096621] usb 2-1.2: firmware: dvb-usb-dib0700-1.20.fw will not be loaded
[53380.096624] dvb-usb: did not find the firmware file. (dvb-usb-dib0700-1.20.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. (-16)