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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <534721.54493.qm@web32602.mail.mud.yahoo.com>
Date:	Mon, 27 Apr 2009 05:34:47 -0700 (PDT)
From:	Martin Knoblauch <knobi@...bisoft.de>
To:	Mel Gorman <mel@....ul.ie>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Michael Chan <mchan@...adcom.com>,
	"David S. Miller" <davem@...emloft.net>
Subject: Re: [BUG] 2.6.30-rc3: bnx2 failing to load firmware


----- Original Message ----

> From: Mel Gorman <mel@....ul.ie>
> To: Linus Torvalds <torvalds@...ux-foundation.org>
> Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>; Michael Chan <mchan@...adcom.com>; David S. Miller <davem@...emloft.net>
> Sent: Friday, April 24, 2009 7:52:39 PM
> Subject: [BUG] 2.6.30-rc3: bnx2 failing to load firmware
> 
> On Tue, Apr 21, 2009 at 08:27:57PM -0700, Linus Torvalds wrote:
> > 
> > Another week, another -rc.
> > 
> 
> Getting this when loading the bnx2 driver
> 
> bnx2 0000:04:00.0: firmware: requesting bnx2/bnx2-mips-06-4.6.16.fw
> bnx2: Can't load firmware file "bnx2/bnx2-mips-06-4.6.16.fw"
> bnx2 0000:04:00.0: PCI INT A disabled
> bnx2: probe of 0000:04:00.0 failed with error -2
> bnx2 0000:06:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
> bnx2 0000:06:00.0: firmware: requesting bnx2/bnx2-mips-06-4.6.16.fw
> bnx2: Can't load firmware file "bnx2/bnx2-mips-06-4.6.16.fw"
> bnx2 0000:06:00.0: PCI INT A disabled
> bnx2: probe of 0000:06:00.0 failed with error -2
> 
> The firmware-related parts of the .config are
> 
> CONFIG_PREVENT_FIRMWARE_BUILD=y
> CONFIG_FIRMWARE_IN_KERNEL=y
> CONFIG_EXTRA_FIRMWARE=""
> CONFIG_FIRMWARE_EDID=y
> CONFIG_FIRMWARE_MEMMAP=y
> 
> Reverting commit 57579f7629a3d46c307405fbd2ea6bdb650d692f "fixes" it no
> doubt there is a better fix. The patch author (Michael) is cc'd but if
> nothing else happens, I'll investigate more after the weekend.
> 
> dmesg and .config attached.
> 

 just curious, what userspace are you using? I have, starting with 2.6.29, a similar problem with tg3. My RHEL4.3 userspace broke hotplugging, because as of 2.6.29 there are two "sysfs" lines in /"proc/mounts". I fixed it in "/etc/hotplug/firmware.agent" by just assuming "/sys" as the "sysfs" mountpoint.

 Maybe of course totally unrelated.

Cheers
Martin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ