Re: [BUG] 2.6.30-rc3: bnx2 failing to load firmware

From: Mel Gorman
Date: Mon Apr 27 2009 - 09:34:05 EST


On Mon, Apr 27, 2009 at 05:34:47AM -0700, Martin Knoblauch wrote:
>
> > From: Mel Gorman <mel@xxxxxxxxx>
> > To: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
> > Cc: Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>; Michael Chan <mchan@xxxxxxxxxxxx>; David S. Miller <davem@xxxxxxxxxxxxx>
> > 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.
>

RHEL 5.3 in this case but it looks like the problem is in mkinitrd and
fixed already for later releases. For testing, I'm just going to build
the network module in and not worry about getting mkinitrd right on this
version of RHEL.

> Maybe of course totally unrelated.
>
> Cheers
> Martin
>

--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/