From: Valdis.Kletnieks@vt.edu
To: David Woodhouse <dwmw2@infradead.org>
Cc: Tigran Aivazian <tigran@aivazian.fsnet.co.uk>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, jonathan@jonmasters.org,
Shaohua Li <shaohua.li@intel.com>,
greg@kroah.com, Kay Sievers <kay.sievers@vrfy.org>,
arjan@infradead.org
Subject: Re: Intel Microcode loader, tg3 driver, and the -rc8-mmotd New World Order firmware...
Date: Thu, 03 Jul 2008 07:34:27 -0400 [thread overview]
Message-ID: <68763.1215084867@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 03 Jul 2008 11:30:29 BST." <1215081029.10393.517.camel@pmac.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On Thu, 03 Jul 2008 11:30:29 BST, David Woodhouse said:
> > Anyhow, it appears the firmware_request() was just a bullet loaded in the
> > chamber waiting for me to pull the trigger 2 years later by setting
> > CONFIG_FIRMWARE_IN_KERNEL=n :)
>
> No, the recent firmware changes haven't modified this. The
> FIRMWARE_IN_KERNEL option makes no difference here.
"D'Oh!" -- H. Simpson.
"Nevermind" - Emily Litella.
Actually, FIRMWARE_IN_KERNEL *did* make a difference - it busticated the tg3
driver and while fighting with the 'firmware: requesting tigon/tg3_tso.bin'
errors I had just inflicted on myself, I found the 'requesting intel-ucode/060f06'
messages as well - and totally failed to notice that the *previous* kernel
and initscripts had *all along* been doing a modprobe, which generated 2 requests
(one per CPU) which failed, and then the initscript ran microcode_ctl *anyhow*,
papering over the two failed requests.. ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2008-07-03 12:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 1:32 Valdis.Kletnieks
2008-07-03 1:43 ` Andrew Morton
2008-07-03 6:17 ` Tigran Aivazian
2008-07-03 6:35 ` Valdis.Kletnieks
2008-07-03 6:44 ` Tigran Aivazian
2008-07-03 9:23 ` David Woodhouse
2008-07-03 10:17 ` Valdis.Kletnieks
2008-07-03 10:30 ` David Woodhouse
2008-07-03 11:34 ` Valdis.Kletnieks [this message]
2008-07-03 12:21 ` David Woodhouse
2008-07-03 12:41 ` Kay Sievers
2008-07-03 12:45 ` David Woodhouse
2008-07-03 13:03 ` Kay Sievers
2008-07-03 13:26 ` David Woodhouse
2008-07-03 13:54 ` Valdis.Kletnieks
2008-07-03 15:23 ` David Woodhouse
2008-07-03 13:48 ` Valdis.Kletnieks
2008-07-03 10:22 ` Kay Sievers
2008-07-03 10:42 ` David Woodhouse
2008-07-03 11:32 ` Kay Sievers
2008-07-03 9:24 ` Giacomo A. Catenazzi
2008-07-03 13:56 ` Arjan van de Ven
2008-07-03 15:54 ` David Woodhouse
2008-07-03 16:22 ` Giacomo A. Catenazzi
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=68763.1215084867@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=jonathan@jonmasters.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=tigran@aivazian.fsnet.co.uk \
/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
all inboxes | Powered by JetHome®