Bug 235482 - (intel_rng) intel_rng: Firmware space is locked read-only
intel_rng: Firmware space is locked read-only
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
6
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-06 00:46 EDT by vikram goyal
Modified: 2008-03-09 06:24 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-03-09 06:24:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
dmesg output (26.33 KB, text/plain)
2007-04-06 00:46 EDT, vikram goyal
no flags Details
/var/log/message under kernel-2.6.20-1.2944.fc6 (39.68 KB, text/plain)
2007-04-19 11:58 EDT, vikram goyal
no flags Details
/var/log/message under kernel-xen-2.6.20-1.2944.fc6 (39.57 KB, text/plain)
2007-04-19 12:01 EDT, vikram goyal
no flags Details

  None (edit)
Description vikram goyal 2007-04-06 00:46:11 EDT
Description of problem:
May be a bug. I'm not sure. If it is not please close it.

Version-Release number of selected component (if applicable):
kernel:
2.6.20-1.2933.fc6

How reproducible:
dmesg attached

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 vikram goyal 2007-04-06 00:46:11 EDT
Created attachment 151823 [details]
dmesg output
Comment 2 Dave Jones 2007-04-09 16:35:48 EDT
as it says, try the 'no_fwh_detect' module option.
What's happened, is that your BIOS has locked part of the PCI config space, so
that new values cannot be written there, and the random number generator driver
needs to write some values to initialise.

You may also find it goes away if there's a newer BIOS update available.
Comment 3 vikram goyal 2007-04-18 13:27:40 EDT
(In reply to comment #2)
> as it says, try the 'no_fwh_detect' module option.
> What's happened, is that your BIOS has locked part of the PCI config space, so
> that new values cannot be written there, and the random number generator driver
> needs to write some values to initialise.
> 
> You may also find it goes away if there's a newer BIOS update available.

OK, I get it, but what's the real outcome. Newer BIOS is not available, as I
checked at intel.com. Since its a kernel thing of which I don't know much.

Shall I let it go? Is there a kernel command line at boot up which I should
insert. Google has not given any info on that except for kernel patches.
Comment 4 Chuck Ebbert 2007-04-18 13:48:50 EDT
> Shall I let it go? Is there a kernel command line at boot up which I should
> insert. Google has not given any info on that except for kernel patches.

Like davej said, did you try the "no_fwh_detect" option?
Comment 5 vikram goyal 2007-04-19 11:58:35 EDT
Created attachment 153019 [details]
/var/log/message under kernel-2.6.20-1.2944.fc6

with intel_rng=no_fwh_detect as kernel arg. System is sluggish with 1.20 load
average per min when it is .20 under previous kernel under normal load
Comment 6 vikram goyal 2007-04-19 12:01:51 EDT
Created attachment 153021 [details]
/var/log/message under kernel-xen-2.6.20-1.2944.fc6

with no_fwh_detect as kernel arg. X never starts under xen kernel

Note You need to log in before you can comment on or make changes to this bug.