public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: "gmu 2k6" <gmu2006@gmail.com>
Cc: "Jeff Garzik" <jgarzik@pobox.com>,
	"Philipp Rumpf" <prumpf@mandrakesoft.com>,
	"Andrew Morton" <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: hwrng on 82801EB/ER (ICH5/ICH5R) fails rngtest checks
Date: Wed, 26 Jul 2006 17:30:31 +0200	[thread overview]
Message-ID: <200607261730.31717.mb@bu3sch.de> (raw)
In-Reply-To: <f96157c40607260752h1cc2a004s8cab09ad7579677e@mail.gmail.com>

On Wednesday 26 July 2006 16:52, gmu 2k6 wrote:
> On 7/26/06, Michael Buesch <mb@bu3sch.de> wrote:
> > On Wednesday 26 July 2006 16:21, gmu 2k6 wrote:
> > > it just outputs this and stops with 2.6.18-rc2-HEAD (see dmesg for hashcode or
> > > whatever that is which is appended as localversion)
> > >
> > > svn:~# hexdump /dev/hwrng
> > > 0000000 ffff ffff ffff ffff ffff ffff ffff ffff
> > > *
> > >
> > > with 2.6.17.6:
> > > svn:~# hexdump /dev/hwrng
> > > 0000000 ffff ffff ffff ffff ffff ffff ffff ffff
> > > *
> > >
> > > this was without any rng-tools installed and no rngd running of course.
> >
> > Hm, so I would say the hardware either broken, or intel
> > changed the way to read the random data from it. But I doubt they
> > would change something like this on the ICH5.
> >
> > Who wrote the ICH driver? Jeff? Philipp?
> > What do you think?
> 
> IIRC it was Jeff.

"What do you think?" was more a question to Jeff or Philipp ;)



But could you try the following patch on top of latest git?
It's just a random test, but I think it's worth trying.
Let's see if it works around the issue.

Index: linux-2.6/drivers/char/hw_random/intel-rng.c
===================================================================
--- linux-2.6.orig/drivers/char/hw_random/intel-rng.c	2006-06-27 17:48:13.000000000 +0200
+++ linux-2.6/drivers/char/hw_random/intel-rng.c	2006-07-26 17:27:03.000000000 +0200
@@ -104,9 +104,14 @@
 	int err = -EIO;
 
 	hw_status = hwstatus_get(mem);
+	hw_status = hwstatus_set(mem, hw_status & ~INTEL_RNG_ENABLED);
+	hw_status = hwstatus_set(mem, hw_status | INTEL_RNG_ENABLED);
+#if 0
+	hw_status = hwstatus_get(mem);
 	/* turn RNG h/w on, if it's off */
 	if ((hw_status & INTEL_RNG_ENABLED) == 0)
 		hw_status = hwstatus_set(mem, hw_status | INTEL_RNG_ENABLED);
+#endif
 	if ((hw_status & INTEL_RNG_ENABLED) == 0) {
 		printk(KERN_ERR PFX "cannot enable RNG, aborting\n");
 		goto out;


-- 
Greetings Michael.

  reply	other threads:[~2006-07-26 15:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060725222209.0048ed15.akpm@osdl.org>
2006-07-26 13:44 ` hwrng on 82801EB/ER (ICH5/ICH5R) fails rngtest checks Michael Buesch
2006-07-26 14:21   ` gmu 2k6
2006-07-26 14:49     ` Michael Buesch
2006-07-26 14:52       ` gmu 2k6
2006-07-26 15:30         ` Michael Buesch [this message]
2006-07-26 15:42           ` gmu 2k6
2006-07-26 19:44           ` gmu 2k6
2006-07-27 13:29             ` Michael Buesch
2006-07-27 14:20               ` gmu 2k6
2006-07-27 14:32                 ` Michael Buesch
2006-07-27 15:07                   ` gmu 2k6
2006-07-26 14:23   ` gmu 2k6
2006-07-25 19:37 gmu 2k6
2006-07-25 19:44 ` gmu 2k6

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=200607261730.31717.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=akpm@osdl.org \
    --cc=gmu2006@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prumpf@mandrakesoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox