Booting 2.6.30-rc2-git7 very slow
----- Original Message ----
Quoted 73 lines
From: Martin Knoblauch <[email protected]>
To: Rafael J. Wysocki <[email protected]>
Cc: [email protected]; [email protected]
Sent: Wednesday, April 22, 2009 1:32:25 PM
Subject: Re: Booting 2.6.30-rc2-git7 very slow----- Original Message ----
Quoted 15 lines
From: Martin Knoblauch
To: Rafael J. Wysocki
Cc: [email protected]
Sent: Wednesday, April 22, 2009 11:56:27 AM
Subject: Re: Booting 2.6.30-rc2-git7 very slowQuoted 9 lines
From: Rafael J. Wysocki
To: Martin Knoblauch
Cc: [email protected]
Sent: Tuesday, April 21, 2009 9:12:20 PM
Subject: Re: Booting 2.6.30-rc2-git7 very slowQuoted 1 line · Martin Knoblauch
Quoted 10 lines
Quoted 3 lines
Quoted 3 lines
Hi, [please CC me on replies, as I am not subscribed]
booting 2.6.30-rc2-git7 on a HP/DL380G3 (
x86_64, RHEL4.3, 64 bituserspace)
Quoted 1 line
is much slower that it used to be. It seems I run into timeouts when [trying
to]
Quoted 3 lines
load intel and tg3 microcodes:
Quoted 2 lines
[ 14.478892] platform microcode: firmware: requestingintel-ucode/0f-04-0a
Quoted 1 line
Quoted 1 line
Quoted 1 line
[ 74.476741] platform microcode: firmware: requestingintel-ucode/0f-04-0a
Quoted 1 line
Quoted 1 line
Quoted 1 line
[ 134.476638] platform microcode: firmware: requestingintel-ucode/0f-04-0a
Quoted 1 line
Quoted 1 line
Quoted 1 line
[ 194.476637] platform microcode: firmware: requestingintel-ucode/0f-04-0a
Quoted 26 lines
Quoted 16 lines
Quoted 1 line
[ 254.476493] Microcode Update Driver: v2.00 ,Peter Oruba
Quoted 14 lines
[ 254.718489] Microcode Update Driver: v2.00 removed.So, we see 60 seconds for eaoch of the CPUs
[ 255.273426] tg3 0000:03:01.0: PME# disabled [ 257.833769] tg3: eth0: Link is up at 1000 Mbps, full duplex. [ 257.833775] tg3: eth0: Flow control is off for TX and off for RX. [ 269.643973] tg3 0000:03:01.1: firmware: requesting tigon/tg3_tso.bin [ 329.640456] eth1: Failed to load firmware "tigon/tg3_tso.bin" [ 329.640463] eth1: TSO capability disabled. [ 329.640487] tg3 0000:03:01.1: PME# disabled [ 333.081753] tg3: eth1: Link is up at 1000 Mbps, full duplex. [ 333.081759] tg3: eth1: Flow control is off for TX and off for RX.Quoted 6 lines
Quoted 3 lines
We see 60 seconds for eth1, complaining about a failed firmware load.
/lib/firmware/tigon/tg3_tso.bindoes exist and is from the current build.Do I assume correctly that 2.6.29 did not have this problem?
Just checked. 2.6.29 has exactely the same problem. 2.6.28.2 was OK. This is from the 2.6.29 boot:
Quoted 6 lines
[ 14.308340] platform microcode: firmware: requesting intel-ucode/0f-04-0a [ 74.304612] platform microcode: firmware: requesting intel-ucode/0f-04-0a [ 134.304651] platform microcode: firmware: requesting intel-ucode/0f-04-0a [ 194.304638] platform microcode: firmware: requesting intel-ucode/0f-04-0a [ 254.304597] Microcode Update Driver: v2.00 , Peter Oruba [ 254.546200] Microcode Update Driver: v2.00 removed.
Quoted 19 lines
In case of the platform microcode, the delays happen when doing:
/sbin/modprobemicrocodefrom the init script. I have a "microcode.dat" File in both
/etc/and/etc/firmware.Quoted 11 lines
[ 255.088405] tg3 0000:03:01.0: PME# disabled [ 257.669617] tg3: eth0: Link is up at 1000 Mbps, full duplex. [ 257.669622] tg3: eth0: Flow control is off for TX and off for RX. [ 269.456132] tg3 0000:03:01.1: firmware: requesting tigon/tg3_tso.bin [ 329.456495] eth1: Failed to load firmware "tigon/tg3_tso.bin" [ 329.456500] eth1: TSO capability disabled. [ 329.456524] tg3 0000:03:01.1: PME# disabled [ 332.921832] tg3: eth1: Link is up at 1000 Mbps, full duplex. [ 332.921837] tg3: eth1: Flow control is off for TX and off for RX.
OK, I was able to solve the tg3 failure by adding "tigon/tg3_tso.bin" to CONFIG_EXTRA_FIRMWARE. I tried the same with the CPU microcode (after copying /etc/firmware/microcode.dat to $BUILDDIR/firmware/), but no success.
Searching the archives also found some mentioning that I might need special udev-rules to make firmware loading work again transparently. But no explicit solution.
I find this new (since 2.6.29) behaviour:
- very unexpected
- not well documented
- the EXTRA_FIRMWARE solution very unscalable
Cheers
Martin