Bug 235482 (intel_rng)
| Summary: | intel_rng: Firmware space is locked read-only | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | vikram goyal <vikigoyal> | ||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 6 | ||||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i386 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2008-03-09 10:24:32 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
vikram goyal
2007-04-06 04:46:11 UTC
Created attachment 151823 [details]
dmesg output
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. (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. > 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?
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
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
|