From: Jeff Garzik <jeff@garzik.org>
To: Hugh Dickins <hugh@veritas.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
mchan@broadcom.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, netdev@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin"
Date: Thu, 03 Jul 2008 09:11:09 -0400 [thread overview]
Message-ID: <486CCFED.7010308@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0807031353030.11033@blonde.site>
Hugh Dickins wrote:
> On Thu, 3 Jul 2008, Jeff Garzik wrote:
>> KOSAKI Motohiro wrote:
>>> Hi Michael,
>>>
>>> my server output following error message on 2.6.26-rc8-mm1.
>>> Is this a bug?
>>>
>>> ------------------------------------------------------------------
>>> tg3.c:v3.93 (May 22, 2008)
>>> GSI 72 (level, low) -> CPU 0 (0x0001) vector 51
>>> tg3 0000:06:01.0: PCI INT A -> GSI 72 (level, low) -> IRQ 51
>>> firmware: requesting tigon/tg3_tso.bin
>>> tg3: Failed to load firmware "tigon/tg3_tso.bin"
>>> tg3 0000:06:01.0: PCI INT A disabled
>>> GSI 72 (level, low) -> CPU 0 (0x0001) vector 51 unregistered
>>> tg3: probe of 0000:06:01.0 failed with error -2
>>> GSI 73 (level, low) -> CPU 0 (0x0001) vector 51
>>> tg3 0000:06:01.1: PCI INT B -> GSI 73 (level, low) -> IRQ 52
>>> firmware: requesting tigon/tg3_tso.bin
>> This change did not come from the network developers or Broadcom, so someone
>> else broke tg3 in -mm...
>
> I think it's a consequence of not choosing CONFIG_FIRMWARE_IN_KERNEL=y.
>
> That caught me out on PowerMac G5 trying mmotm yesterday, it just hung
> for a few minutes in earlyish boot with a message about tg3_tso.bin,
> and then proceeded to boot up but without the network. I was unclear
> whether I'd been stupid, or the FIRMWARE_IN_KERNEL Kconfigery was poor.
>
> I avoid initrd, and have tigon3 built in, if that's of any relevance.
>
> I wonder if that's Andrew's problem with 2.6.26-rc8-mm1 on his G5:
> mine here boots up fine (now I know to CONFIG_FIRMWARE_IN_KERNEL=y).
dwmw2 has been told repeatedly that his changes will cause PRECISELY
these problems, but he refuses to take the simple steps necessary to
ensure people can continue to boot their kernels after his changes go in.
Presently his tg3 changes have been nak'd, in part, because of this
obviously, forseeable, work-around-able breakage.
Jeff
next prev parent reply other threads:[~2008-07-03 13:11 UTC|newest]
Thread overview: 142+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080703020236.adaa51fa.akpm@linux-foundation.org>
2008-07-03 11:59 ` [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" KOSAKI Motohiro
2008-07-03 12:21 ` Jeff Garzik
2008-07-03 13:04 ` Hugh Dickins
2008-07-03 13:11 ` Jeff Garzik [this message]
2008-07-03 13:33 ` David Woodhouse
2008-07-03 13:38 ` Jeff Garzik
2008-07-03 13:52 ` David Woodhouse
2008-07-03 17:30 ` Theodore Tso
2008-07-03 18:56 ` David Woodhouse
2008-07-03 19:31 ` Valdis.Kletnieks
2008-07-03 19:49 ` David Woodhouse
2008-07-03 20:52 ` Rafael J. Wysocki
2008-07-03 21:03 ` Jeff Garzik
2008-07-03 21:33 ` David Woodhouse
2008-07-03 21:42 ` Rafael J. Wysocki
2008-07-03 21:43 ` David Woodhouse
2008-07-03 21:52 ` Rafael J. Wysocki
2008-07-03 21:54 ` David Woodhouse
2008-07-03 22:27 ` Rafael J. Wysocki
2008-07-03 22:22 ` Jeff Garzik
2008-07-03 22:25 ` Alan Cox
2008-07-03 23:14 ` Jeff Garzik
2008-07-03 23:02 ` Alan Cox
2008-07-04 2:31 ` Mikael Pettersson
2008-07-03 23:21 ` David Miller
2008-07-04 0:18 ` Theodore Tso
2008-07-04 1:09 ` David Woodhouse
2008-07-04 1:47 ` Theodore Tso
2008-07-04 0:24 ` David Woodhouse
2008-07-04 1:28 ` Grant Coady
2008-07-04 2:42 ` david
2008-07-04 10:07 ` David Woodhouse
2008-07-04 10:09 ` Andi Kleen
2008-07-04 13:10 ` David Woodhouse
2008-07-04 13:15 ` Jeff Garzik
2008-07-04 13:27 ` David Woodhouse
2008-07-04 13:39 ` Jeff Garzik
2008-07-04 13:27 ` Alan Cox
2008-07-04 13:48 ` David Woodhouse
2008-07-04 14:06 ` Jeff Garzik
2008-07-04 20:43 ` David Miller
2008-07-04 21:04 ` Alan Cox
2008-07-06 20:17 ` david
2008-07-06 20:27 ` David Woodhouse
2008-07-06 20:51 ` Jeff Garzik
2008-07-06 20:52 ` david
2008-07-06 20:56 ` David Woodhouse
2008-07-06 21:03 ` david
2008-07-06 21:38 ` Jeff Garzik
2008-07-06 22:10 ` David Woodhouse
2008-07-06 23:22 ` Jeff Garzik
2008-07-05 6:05 ` Jeff Garzik
2008-07-07 17:52 ` Rick Jones
2008-07-04 13:46 ` David Woodhouse
2008-07-04 14:07 ` Jeff Garzik
2008-07-04 14:38 ` Alan Cox
2008-07-06 23:40 ` Jeff Garzik
2008-07-07 15:53 ` Alan Cox
2008-07-07 17:24 ` Jeff Garzik
2008-07-07 18:13 ` Alan Cox
2008-07-07 18:57 ` Jeff Garzik
2008-07-07 18:30 ` Alan Cox
2008-07-07 19:16 ` Jeff Garzik
2008-07-07 18:45 ` Alan Cox
2008-07-07 19:48 ` Jeff Garzik
2008-07-07 20:48 ` David Miller
2008-07-07 20:42 ` Alan Cox
2008-07-07 21:45 ` David Miller
2008-07-07 21:14 ` Alan Cox
2008-07-07 21:58 ` David Miller
2008-07-08 6:36 ` Alan Cox
2008-07-08 8:57 ` David Miller
2008-07-04 14:30 ` Theodore Tso
2008-07-04 14:37 ` David Woodhouse
2008-07-04 18:01 ` David Woodhouse
2008-07-04 20:28 ` Sam Ravnborg
2008-07-05 4:35 ` Jeff Garzik
2008-07-04 20:39 ` David Miller
2008-07-04 14:10 ` Theodore Tso
2008-07-04 14:23 ` Takashi Iwai
2008-07-04 14:39 ` Hannes Reinecke
2008-07-04 14:42 ` David Woodhouse
2008-07-04 21:34 ` Grant Coady
2008-07-04 22:08 ` David Woodhouse
2008-07-04 23:13 ` Olivier Galibert
2008-07-04 23:58 ` Henrique de Moraes Holschuh
[not found] ` <20080704235839.GA5649@khazad-dum.debian.net>
2008-07-05 0:51 ` Trent Piepho
2008-07-05 3:52 ` Henrique de Moraes Holschuh
2008-07-05 6:01 ` Bill Fink
2008-07-05 13:08 ` Henrique de Moraes Holschuh
2008-07-05 4:10 ` Jeff Garzik
2008-07-05 7:41 ` Takashi Iwai
2008-07-05 8:50 ` David Woodhouse
2008-07-05 10:53 ` Olivier Galibert
2008-07-05 11:22 ` Andi Kleen
2008-07-05 12:02 ` Olivier Galibert
2008-07-05 12:09 ` Andi Kleen
2008-07-05 12:16 ` David Woodhouse
2008-07-05 12:23 ` Andi Kleen
2008-07-05 12:42 ` David Woodhouse
2008-07-05 13:57 ` Andi Kleen
2008-07-05 14:44 ` Olivier Galibert
2008-07-05 15:10 ` David Woodhouse
2008-07-05 17:13 ` Christoph Hellwig
2008-07-05 20:55 ` David Woodhouse
2008-07-06 10:02 ` Christoph Hellwig
2008-07-06 10:55 ` David Woodhouse
2008-07-06 11:50 ` Andi Kleen
2008-07-06 12:22 ` David Woodhouse
2008-07-04 14:44 ` Takashi Iwai
2008-07-04 14:24 ` maximilian attems
2008-07-04 14:36 ` Theodore Tso
2008-07-05 10:26 ` maximilian attems
2008-07-04 14:31 ` David Woodhouse
2008-07-04 20:37 ` David Miller
2008-07-04 20:42 ` Arjan van de Ven
2008-07-04 20:43 ` David Woodhouse
2008-07-04 20:52 ` David Miller
2008-07-04 21:05 ` David Woodhouse
2008-07-05 4:05 ` Valdis.Kletnieks
2008-07-04 20:51 ` David Miller
2008-07-04 20:59 ` Arjan van de Ven
2008-07-04 21:12 ` David Woodhouse
2008-07-04 21:10 ` Alan Cox
2008-07-04 20:53 ` David Woodhouse
2008-07-05 4:04 ` Jeff Garzik
2008-07-04 13:42 ` Andi Kleen
2008-07-03 20:34 ` David Miller
2008-07-03 20:54 ` David Woodhouse
2008-07-09 20:43 ` Alexandre Oliva
2008-07-04 11:06 ` Takashi Iwai
2008-07-04 13:17 ` David Woodhouse
2008-07-04 13:26 ` Takashi Iwai
2008-07-04 13:28 ` David Woodhouse
2008-07-04 13:42 ` Jeff Garzik
2008-07-04 13:45 ` David Woodhouse
2008-07-04 14:10 ` Jeff Garzik
2008-07-04 14:13 ` David Woodhouse
2008-07-05 6:14 ` Jeff Garzik
2008-07-04 13:28 ` Jeff Garzik
2008-07-03 16:10 ` Chuck Lever
2008-07-05 5:49 Jaswinder Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=486CCFED.7010308@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=hugh@veritas.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).