Bug#708610: linux-image: During resume `WARNING: at …linux-3.2.41/drivers/base/firmware_class.c:547 _request_firmware+0xd5/0x3cc()`
Control: tag -1 upstream fixed-upstream
On Fri, 2013-05-17 at 09:29 +0200, Paul Menzel wrote:
> Package: src:linux
> Version: 3.2.41-2+deb7u2
> Severity: important
>
> Dear Debian folks,
>
>
> resuming from suspend to RAM with `sudo pm-suspend`, I see the following
> warning in the Linux kernel ring buffer.
>
> [ 2666.656607] WARNING: at /build/buildd-linux_3.2.41-2+deb7u2-i386-G4jjsr/linux-3.2.41/drivers/base/firmware_class.c:547 _request_firmware+0xd5/0x3cc()
> [ 2666.656610] Hardware name: To Be Filled By O.E.M.
> [ 2666.656611] Modules linked in: arc4 nouveau rtl8192cu rtlwifi rtl8192c_common mxm_wmi mac80211 wmi video snd_ice1712 ttm snd_cs8427 snd_i2c drm_kms_helper snd_ice17xx_ak4xxx snd_ak4xxx_adda snd_ac97_codec cfg80211 drm snd_mpu401_uart acpi_cpufreq mperf iTCO_wdt rfkill snd_rawmidi iTCO_vendor_support snd_seq_device i2c_i801 power_supply snd_pcm i2c_algo_bit parport_pc snd_page_alloc snd_timer parport processor ac97_bus i2c_core snd button soundcore thermal_sys rng_core coretemp evdev ext4 crc16 jbd2 mbcache sha256_generic cryptd aes_x86_64 aes_generic cbc ohci_hcd usbhid hid dm_crypt dm_mod sg sr_mod cdrom sd_mod crc_t10dif ata_generic uhci_hcd ata_piix libata ehci_hcd r8169 mii scsi_mod usbcore usb_common [last unloaded: pcspkr]
> [ 2666.656648] Pid: 22324, comm: pm-suspend Not tainted 3.2.0-4-amd64 #1 Debian 3.2.41-2+deb7u2
> [ 2666.656650] Call Trace:
> [ 2666.656655] [<ffffffff81046971>] ? warn_slowpath_common+0x78/0x8c
> [ 2666.656658] [<ffffffff81255fc7>] ? _request_firmware+0xd5/0x3cc
> [ 2666.656662] [<ffffffffa0451e33>] ? rtl92cu_init_sw_vars+0xd4/0x181 [rtl8192cu]
> [ 2666.656666] [<ffffffffa039820d>] ? rtl_usb_probe+0x1cb/0xfbe [rtlwifi]
> [ 2666.656669] [<ffffffff81255438>] ? __pm_runtime_set_status+0x118/0x13c
> [ 2666.656677] [<ffffffffa0075676>] ? usb_probe_interface+0xf2/0x15d [usbcore]
> [ 2666.656680] [<ffffffff8124db05>] ? driver_probe_device+0xa8/0x138
> [ 2666.656683] [<ffffffff8124dc04>] ? __driver_attach+0x6f/0x6f
> [ 2666.656685] [<ffffffff8124c6b1>] ? bus_for_each_drv+0x47/0x7b
> [ 2666.656687] [<ffffffff8124da26>] ? device_attach+0x6f/0x8f
> [ 2666.656694] [<ffffffffa00753dd>] ? usb_rebind_intf+0x35/0x4f [usbcore]
> [ 2666.656700] [<ffffffffa0075468>] ? do_unbind_rebind.isra.9+0x54/0x64 [usbcore]
> [ 2666.656706] [<ffffffffa00754d8>] ? usb_resume+0x60/0x72 [usbcore]
> [ 2666.656712] [<ffffffffa006b08c>] ? usb_dev_resume+0xf/0xf [usbcore]
> [ 2666.656717] [<ffffffffa006b095>] ? usb_dev_complete+0x9/0xc [usbcore]
> [ 2666.656720] [<ffffffff812532b1>] ? dpm_complete+0xd2/0x141
> [ 2666.656723] [<ffffffff81076dd3>] ? suspend_devices_and_enter+0x1c6/0x207
> [ 2666.656726] [<ffffffff81076f2f>] ? enter_state+0x11b/0x15c
> [ 2666.656728] [<ffffffff81075f63>] ? state_store+0xb7/0x101
> [ 2666.656731] [<ffffffff8114d06f>] ? sysfs_write_file+0xe0/0x11c
> [ 2666.656735] [<ffffffff810f9249>] ? vfs_write+0xa2/0xe9
> [ 2666.656737] [<ffffffff810f9426>] ? sys_write+0x45/0x6b
> [ 2666.656740] [<ffffffff81350423>] ? ia32_do_call+0x13/0x13
[...]
The driver is requesting firmware during probe, but it's being probed
during resume at which point user-space programs are stopped and the
kernel can't request firmware.
This is probably fixed upstream, either in the driver or by the kernel
being able to load firmware by direct file access.
Ben.
--
Ben Hutchings
Editing code like this is akin to sticking plasters on the bleeding stump
of a severed limb. - me, 29 June 1999
Reply to: