netdev - e100 fail in 2.6.29-rc6-git7, kernel requesting firmware

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <200903080010.13280.denys@visp.net.lb>
Date:	Sun, 8 Mar 2009 00:10:13 +0200
From:	Denys Fedoryschenko <denys@...p.net.lb>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	jeffrey.t.kirsher@...el.com, e1000-devel@...ts.sourceforge.net
Subject: e100 fail in 2.6.29-rc6-git7, kernel requesting firmware

Kernel 2.6.29-rc6-git7

It will get stuck at 
[   11.798229] e100 0000:05:04.0: firmware: requesting e100/d101m_ucode.bin

GlobalOS ~ # zcat /proc/config.gz |grep FIRM
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
CONFIG_FIRMWARE_MEMMAP=y

Most important point:
│ CONFIG_FIRMWARE_IN_KERNEL:                                                                                                                                                                          
│ The kernel source tree includes a number of firmware 'blobs'                                                                                                                                        
│ which are used by various drivers. The recommended way to                                                                                                                                           
│ use these is to run "make firmware_install" and to copy the                                                                                                                                         
│ resulting binary files created in usr/lib/firmware directory                                                                                                                                        
│ of the kernel tree to the /lib/firmware on your system so                                                                                                                                           
│ that they can be loaded by userspace helpers on request.                                                                                                                                            
│ Enabling this option will build each required firmware blob                                                                                                                                         
│ into the kernel directly, where request_firmware() will find                                                                                                                                        
│ them without having to call out to userspace. This may be                                                                                                                                           
│ useful if your root file system requires a device which uses                                                                                                                                        
│ such firmware, and do not wish to use an initrd.                                                                                                                                                  

Another thing, while requesting firmware, if firmware file not available, all 
networking and kernel tasks is dying (no keyboards events, traffic not 
passing over and etc). I dont think it is normal behavior.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html