>From the log:
Mar 24 09:02:42 proxy-cvk-2 kernel: [ 39.078323] tg3 0000:02:02.0: PME# disabled
Mar 24 09:02:42 proxy-cvk-2 kernel: [ 40.600196] tg3 0000:02:02.1: firmware: requesting tigon/tg3_tso.bin
Mar 24 09:02:42 proxy-cvk-2 kernel: [ 41.723404] tg3: eth0: Link is up at 1000 Mbps, full duplex.
Mar 24 09:02:42 proxy-cvk-2 kernel: [ 41.723458] tg3: eth0: Flow control is on for TX and on for RX.
Mar 24 09:02:42 proxy-cvk-2 kernel: [ 100.599130] eth1: Failed to load firmware "tigon/tg3_tso.bin"
Mar 24 09:02:42 proxy-cvk-2 kernel: [ 100.599184] eth1: TSO capability disabled.
Mar 24 09:02:42 proxy-cvk-2 kernel: [ 100.599241] tg3 0000:02:02.1: PME# disabled
but:
# ll /lib/firmware/2.6.29/tigon/tg3_tso.bin
-rw-r--r-- 1 root root 7004 Mar 24 09:24 /lib/firmware/2.6.29/tigon/tg3_tso.bin
On Tue, 24 Mar 2009 13:09:48 +0100
Ralf Hildebrandt <[email protected]> wrote:
> >From the log:
>
> Mar 24 09:02:42 proxy-cvk-2 kernel: [ 39.078323] tg3 0000:02:02.0: PME# disabled
> Mar 24 09:02:42 proxy-cvk-2 kernel: [ 40.600196] tg3 0000:02:02.1: firmware: requesting tigon/tg3_tso.bin
> Mar 24 09:02:42 proxy-cvk-2 kernel: [ 41.723404] tg3: eth0: Link is up at 1000 Mbps, full duplex.
> Mar 24 09:02:42 proxy-cvk-2 kernel: [ 41.723458] tg3: eth0: Flow control is on for TX and on for RX.
> Mar 24 09:02:42 proxy-cvk-2 kernel: [ 100.599130] eth1: Failed to load firmware "tigon/tg3_tso.bin"
> Mar 24 09:02:42 proxy-cvk-2 kernel: [ 100.599184] eth1: TSO capability disabled.
> Mar 24 09:02:42 proxy-cvk-2 kernel: [ 100.599241] tg3 0000:02:02.1: PME# disabled
>
> but:
>
> # ll /lib/firmware/2.6.29/tigon/tg3_tso.bin
> -rw-r--r-- 1 root root 7004 Mar 24 09:24 /lib/firmware/2.6.29/tigon/tg3_tso.bin
Is your userspace configured to use /lib/firmware/2.6.29 or the more
usual /lib/firmware/ ?
Ralf Hildebrandt wrote:
> From the log:
>
> Mar 24 09:02:42 proxy-cvk-2 kernel: [ 40.600196] tg3 0000:02:02.1: firmware: requesting tigon/tg3_tso.bin
> Mar 24 09:02:42 proxy-cvk-2 kernel: [ 100.599130] eth1: Failed to load firmware "tigon/tg3_tso.bin"
> # ll /lib/firmware/2.6.29/tigon/tg3_tso.bin
> -rw-r--r-- 1 root root 7004 Mar 24 09:24 /lib/firmware/2.6.29/tigon/tg3_tso.bin
Shouldn't it be in /lib/firmware/tigon/tg3_tso.bin ?
I mean, are you sure it's kernel and not userspace (udev?) issue?
Starting with 2.6.29, tg3 does not include firmware in the kernel anymore,
as happened with many other drivers already - that was a change for sure.
(which reminds me I have to rework diskless initrd *again* shrug)
/mjt
* Alan Cox <[email protected]>:
> On Tue, 24 Mar 2009 13:09:48 +0100
> Ralf Hildebrandt <[email protected]> wrote:
>
> > >From the log:
> >
> > Mar 24 09:02:42 proxy-cvk-2 kernel: [ 39.078323] tg3 0000:02:02.0: PME# disabled
> > Mar 24 09:02:42 proxy-cvk-2 kernel: [ 40.600196] tg3 0000:02:02.1: firmware: requesting tigon/tg3_tso.bin
> > Mar 24 09:02:42 proxy-cvk-2 kernel: [ 41.723404] tg3: eth0: Link is up at 1000 Mbps, full duplex.
> > Mar 24 09:02:42 proxy-cvk-2 kernel: [ 41.723458] tg3: eth0: Flow control is on for TX and on for RX.
> > Mar 24 09:02:42 proxy-cvk-2 kernel: [ 100.599130] eth1: Failed to load firmware "tigon/tg3_tso.bin"
> > Mar 24 09:02:42 proxy-cvk-2 kernel: [ 100.599184] eth1: TSO capability disabled.
> > Mar 24 09:02:42 proxy-cvk-2 kernel: [ 100.599241] tg3 0000:02:02.1: PME# disabled
> >
> > but:
> >
> > # ll /lib/firmware/2.6.29/tigon/tg3_tso.bin
> > -rw-r--r-- 1 root root 7004 Mar 24 09:24 /lib/firmware/2.6.29/tigon/tg3_tso.bin
>
> Is your userspace configured to use /lib/firmware/2.6.29 or the more
> usual /lib/firmware/ ?
Which leads to the next question: How to I find out?
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12200 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
[email protected] | http://www.charite.de
* Michael Tokarev <[email protected]>:
> Ralf Hildebrandt wrote:
>> From the log:
>>
>> Mar 24 09:02:42 proxy-cvk-2 kernel: [ 40.600196] tg3 0000:02:02.1: firmware: requesting tigon/tg3_tso.bin
>> Mar 24 09:02:42 proxy-cvk-2 kernel: [ 100.599130] eth1: Failed to load firmware "tigon/tg3_tso.bin"
>
>> # ll /lib/firmware/2.6.29/tigon/tg3_tso.bin
>> -rw-r--r-- 1 root root 7004 Mar 24 09:24 /lib/firmware/2.6.29/tigon/tg3_tso.bin
>
> Shouldn't it be in /lib/firmware/tigon/tg3_tso.bin ?
Well, who knows...
proxy-cvk-1:/lib/firmware# cp -a 2.6.29/tigon .
proxy-cvk-1:/lib/firmware# ll
total 12
drwxr-xr-x 3 root root 4096 Mar 24 09:24 2.6.29
drwxr-xr-x 3 root root 4096 Mar 17 16:31 2.6.29-rc8-git2
drwxr-xr-x 2 root root 4096 Mar 24 09:24 tigon
Let's see if that work.s
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12200 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
[email protected] | http://www.charite.de
* Ralf Hildebrandt <[email protected]>:
> * Michael Tokarev <[email protected]>:
> > Ralf Hildebrandt wrote:
> >> From the log:
> >>
> >> Mar 24 09:02:42 proxy-cvk-2 kernel: [ 40.600196] tg3 0000:02:02.1: firmware: requesting tigon/tg3_tso.bin
> >> Mar 24 09:02:42 proxy-cvk-2 kernel: [ 100.599130] eth1: Failed to load firmware "tigon/tg3_tso.bin"
> >
> >> # ll /lib/firmware/2.6.29/tigon/tg3_tso.bin
> >> -rw-r--r-- 1 root root 7004 Mar 24 09:24 /lib/firmware/2.6.29/tigon/tg3_tso.bin
> >
> > Shouldn't it be in /lib/firmware/tigon/tg3_tso.bin ?
>
> Well, who knows...
>
> proxy-cvk-1:/lib/firmware# cp -a 2.6.29/tigon .
> proxy-cvk-1:/lib/firmware# ll
> total 12
> drwxr-xr-x 3 root root 4096 Mar 24 09:24 2.6.29
> drwxr-xr-x 3 root root 4096 Mar 17 16:31 2.6.29-rc8-git2
> drwxr-xr-x 2 root root 4096 Mar 24 09:24 tigon
>
> Let's see if that work.s
Nope, doesn't. Still the same.
[ 6.637970] tg3 0000:02:02.0: PME# disabled
[ 8.175091] tg3 0000:02:02.1: firmware: requesting tigon/tg3_tso.bin
[ 9.198453] tg3: eth0: Link is up at 1000 Mbps, full duplex.
[ 9.198507] tg3: eth0: Flow control is on for TX and on for RX.
[ 68.174144] eth1: Failed to load firmware "tigon/tg3_tso.bin"
[ 68.174206] eth1: TSO capability disabled.
[ 68.174274] tg3 0000:02:02.1: PME# disabled
[ 71.070553] tg3: eth1: Link is up at 1000 Mbps, full duplex.
[ 71.070608] tg3: eth1: Flow control is on for TX and on for RX.
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12200 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
[email protected] | http://www.charite.de
> > Is your userspace configured to use /lib/firmware/2.6.29 or the more
> > usual /lib/firmware/ ?
>
> Which leads to the next question: How to I find out?
Consult your distribution ? or stick it in both places and see 8)
* Alan Cox <[email protected]>:
> > > Is your userspace configured to use /lib/firmware/2.6.29 or the more
> > > usual /lib/firmware/ ?
> >
> > Which leads to the next question: How to I find out?
>
> Consult your distribution ? or stick it in both places and see 8)
Did that. No workee.
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12200 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
[email protected] | http://www.charite.de
* Ralf Hildebrandt <[email protected]>:
> * Alan Cox <[email protected]>:
> > > > Is your userspace configured to use /lib/firmware/2.6.29 or the more
> > > > usual /lib/firmware/ ?
> > >
> > > Which leads to the next question: How to I find out?
> >
> > Consult your distribution ? or stick it in both places and see 8)
>
> Did that. No workee.
I mean, loading the firmware is not SOOO important. The thing that
annoys me is the 60 delay introduced by that.
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12200 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
[email protected] | http://www.charite.de
Ralf Hildebrandt wrote:
> * Ralf Hildebrandt <[email protected]>:
>> * Alan Cox <[email protected]>:
>>>>> Is your userspace configured to use /lib/firmware/2.6.29 or the more
>>>>> usual /lib/firmware/ ?
>>>> Which leads to the next question: How to I find out?
>>> Consult your distribution ? or stick it in both places and see 8)
>> Did that. No workee.
>
> I mean, loading the firmware is not SOOO important. The thing that
> annoys me is the 60 delay introduced by that.
Damn.
I missed that thing in your initial message.
It's the delay. It's here!
The thing is that you don't run any hotplug handler.
No udev or mdev.
Hence no on handles that firmware loading request.
Hence the kernel waits and times out...
Oh well.
/mjt