From: Dmitry Adamushko <dmitry.adamushko@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Zdenek Kabelac <zdenek.kabelac@gmail.com>,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Rusty Russell <rusty@rustcorp.com.au>,
Ingo Molnar <mingo@elte.hu>, Kay Sievers <kay.sievers@vrfy.org>,
Greg KH <greg@kroah.com>
Subject: Re: WARNING: at fs/sysfs/group.c:138 sysfs_remove_group
Date: Fri, 24 Apr 2009 10:46:33 +0200 [thread overview]
Message-ID: <b647ffbd0904240146mdcb84f7mcefa0850da425155@mail.gmail.com> (raw)
In-Reply-To: <20090423130930.50a6c9db.akpm@linux-foundation.org>
2009/4/23 Andrew Morton <akpm@linux-foundation.org>:
> On Fri, 17 Apr 2009 11:13:08 +0200
> Zdenek Kabelac <zdenek.kabelac@gmail.com> wrote:
>
>> Hi
>>
>>
>> When I've checked 2.6.30-rc2 kernel and I've got among other errors
>> with Wifi message below.
>> As I've noticed - some people were reporting this problem already earlier:
>>
>> http://www.gossamer-threads.com/lists/linux/kernel/1058276?page=last
>>
>> But for me - it started with 2.6.30-rc kernels.
>> I've T61, 4GB, C2D, X86_64.
>>
>>
>>
>> Zdenek
>>
>>
>> platform microcode: firmware: requesting intel-ucode/06-0f-0a
>> platform microcode: firmware: requesting intel-ucode/06-0f-0a
>
> Lots of people are reporting this. One person reported that each
> attempt takes 60 seconds, thus delaying boot be several minutes.
These microcode messages are normal per-se.
>From the original report [1] follows that there is another 60s. delay
when loading a firmware for an eth device.
[quote]
[ 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"
...
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.
[/quote]
IOW, the issue likely has something to do with firmware loading in general.
--
Best regards,
Dmitry Adamushko
next prev parent reply other threads:[~2009-04-24 8:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 9:13 WARNING: at fs/sysfs/group.c:138 sysfs_remove_group Zdenek Kabelac
2009-04-23 20:09 ` Andrew Morton
2009-04-23 20:39 ` Greg KH
2009-04-23 21:01 ` Andrew Morton
2009-04-24 7:31 ` Ingo Molnar
2009-04-24 8:32 ` Dmitry Adamushko
2009-04-24 8:38 ` Ingo Molnar
2009-04-24 8:46 ` Dmitry Adamushko [this message]
2009-04-24 8:48 ` Dmitry Adamushko
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=b647ffbd0904240146mdcb84f7mcefa0850da425155@mail.gmail.com \
--to=dmitry.adamushko@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=rusty@rustcorp.com.au \
--cc=zdenek.kabelac@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.