From: David Ford <david+cert@blue-labs.org>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: 2.5.66 buglet
Date: Wed, 26 Mar 2003 23:23:54 -0500 [thread overview]
Message-ID: <3E827CDA.8030904@blue-labs.org> (raw)
<boot dmesg snip>
devfs_register(cpu/microcode): illegal mode: 8180
</snip>
# ls /dev/cpu
# grep -i microcode /boot/2.5.66/.config
CONFIG_MICROCODE=y
Not sure how it breaks between .64 where it worked and .66 where it
doesn't. The code where it's registered doesn't appear to have changed.
arch/i386/kernel/microcode.c, line 137.
david
next reply other threads:[~2003-03-27 4:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 4:23 David Ford [this message]
2003-03-27 14:54 ` 2.5.66 buglet Christoph Hellwig
2003-03-27 23:30 ` Dave Jones
2003-03-28 8:26 ` Christoph Hellwig
2003-03-28 11:11 ` Dave Jones
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=3E827CDA.8030904@blue-labs.org \
--to=david+cert@blue-labs.org \
--cc=linux-kernel@vger.kernel.org \
/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