LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Martin Bretschneider <martin.bretschneider@imr.uni-hannover.de>
To: linux-kernel@vger.kernel.org, jgarzik@pobox.com,
jbeulich@novell.com, mb@bu3sch.de
Subject: new HW RNG freezes kernels > 2.6.17 at startup with Xeon 5130
Date: Mon, 15 Jan 2007 13:07:40 +0100 [thread overview]
Message-ID: <45AB6E8C.4090408@imr.uni-hannover.de> (raw)
Hi,
it seems to me that the new hardware random number generator (HW RNG)
freezes my hardware:
The CPU is Intel Xeon 5130 (Intel Core microarchitecture) [1] installed
on Intel Server Board S5000VSA.
Linux is run in 64bit mode and the distribution is Debian Etch (but that
should not matter).
If I take Debian's kernel 2.6.17 it boots :-)
If I take vanilla kernel 2.6.17.9 it boots :-)
If I take Debian's kernel 2.6.18 it does not boot.
If I take vanilla kernel 2.6.18.6 it does not boot.
If I take vanilla kernel 2.6.19.1 it does not boot.
If I take vanilla kernel 2.6.20-rc4 it does not boot.
There was no error thus it was not that easy to find out the problem.
Comparing the boot logs of 2.6.17 and 2.6.18 the freeze ocurred before
initializing the hardware random number generator. Thus I recompiled the
vanilla Kernel 2.6.18.6 without support of the new HW RNG and it boots.
So, I renamed the directory /kernel/drivers/char/hw_random and the
Debian kernel 2.6.18 does also boot.
I have not testet the kernel > 2.6.18 but I guess that they will also
boot without the new NW RNG.
Do you know the problem? Can I provide you more information?
TIA Martin
[1]http://en.wikipedia.org/wiki/List_of_Intel_Xeon_microprocessors#Woodcrest
next reply other threads:[~2007-01-15 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 12:07 Martin Bretschneider [this message]
2007-01-15 13:12 ` Jan Beulich
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=45AB6E8C.4090408@imr.uni-hannover.de \
--to=martin.bretschneider@imr.uni-hannover.de \
--cc=jbeulich@novell.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--subject='Re: new HW RNG freezes kernels > 2.6.17 at startup with Xeon 5130' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).