From: Martin Knoblauch <spamtrap@knobisoft.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, efault@gmx.de
Subject: Re: Booting 2.6.30-rc2-git7 very slow
Date: Wed, 22 Apr 2009 04:32:25 -0700 (PDT) [thread overview]
Message-ID: <808633.38942.qm@web32605.mail.mud.yahoo.com> (raw)
----- Original Message ----
> From: Martin Knoblauch <spamtrap@knobisoft.de>
> To: Rafael J. Wysocki <rjw@sisk.pl>
> Cc: linux-kernel@vger.kernel.org
> Sent: Wednesday, April 22, 2009 11:56:27 AM
> Subject: Re: Booting 2.6.30-rc2-git7 very slow
>
> > From: Rafael J. Wysocki
>
> > To: Martin Knoblauch
> > Cc: linux-kernel@vger.kernel.org
> > Sent: Tuesday, April 21, 2009 9:12:20 PM
> > Subject: Re: Booting 2.6.30-rc2-git7 very slow
> >
> > On Tuesday 21 April 2009, Martin Knoblauch wrote:
> > >
> > > 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 bit
> userspace)
> > is much slower that it used to be. It seems I run into timeouts when [trying
> to]
> > load intel and tg3 microcodes:
> > >
> > > [ 14.478892] platform microcode: firmware: requesting intel-ucode/0f-04-0a
> > > [ 74.476741] platform microcode: firmware: requesting intel-ucode/0f-04-0a
> > > [ 134.476638] platform microcode: firmware: requesting intel-ucode/0f-04-0a
> > > [ 194.476637] platform microcode: firmware: requesting intel-ucode/0f-04-0a
> > > [ 254.476493] Microcode Update Driver: v2.00 ,
> > Peter Oruba
> > > [ 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.
> > >
> > > We see 60 seconds for eth1, complaining about a failed firmware load.
> > > /lib/firmware/tigon/tg3_tso.bin does 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:
>
> [ 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.
In case of the platform microcode, the delays happen when doing:
/sbin/modprobe microcode
from the init script. I have a "microcode.dat" File in both /etc/ and /etc/firmware.
> [ 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.
>
>
Thanks
Martin
next reply other threads:[~2009-04-22 11:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 11:32 Martin Knoblauch [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-22 16:55 Booting 2.6.30-rc2-git7 very slow Martin Knoblauch
2009-04-22 6:06 Martin Knoblauch
2009-04-21 14:21 Martin Knoblauch
2009-04-21 14:32 ` Martin Knoblauch
2009-04-21 19:12 ` Rafael J. Wysocki
2009-04-22 9:56 ` Martin Knoblauch
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=808633.38942.qm@web32605.mail.mud.yahoo.com \
--to=spamtrap@knobisoft.de \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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