Bug 442190
Summary: | padlock drivers noisy on encrypted root boot with non-VIA cpus | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | louisgtwo |
Component: | module-init-tools | Assignee: | Jon Masters <jcm> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | bugs+fedora, dcantrell, dlehman, george.king, jcm, johannbg, katzj, pcfe, wtogami, wwoods |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | module-init-tools-3.4-13.fc9 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-05-02 17:42:47 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: | |||
Bug Depends On: | |||
Bug Blocks: | 235706 |
Description
louisgtwo
2008-04-12 15:34:34 UTC
No, the aes-generic and sha256-generic modules get loaded also. But we try to load all modules matching the alias which provide the sha256 modalias (and aes) which includes the padlock modules which are for VIA hardware acceleration. There's not really any great ways to avoid this Well how about silencing the errors. This looks a bit unprofesional. *** Bug 443905 has been marked as a duplicate of this bug. *** *** Bug 443092 has been marked as a duplicate of this bug. *** If we're going to quiet things anywhere, it should probably be modprobe. Um. I'm not able to reproduce at the moment - looks like davej or chuck changed the kernel config to stop building these padlock drivers? But what you're asking for is a valid feature. I won't rush out to fix this tonight if this isn't actually a blocker for F9. As mentioned to jcm privately -- they're still there and built on x86 but obviously not on x86_64 and ppc (via only makes x86 hardware) And wwoods -- on the blocker list because otherwise, we're going to get a deluge of reports about this. With quiet disabled earlier in the cycle, no one noticed. But it's a very very visible thing in a new feature that we're pretty heavily touting. Unless we're "happy" dealing with that, it needs to be fixed It's on my TODO for tomorrow. I'll have to install a 32-bit rawhide tonight to reproduce - I had foolishly not considered that VIA only make 32-bit hardware :) Ok, I can reproduce this now. Looking into it. I've posted a fix, which I'll want to rework for upstream, but this should be ok for F-9 use. If I get the other fix done today, I'll request another update. if you are referring to module-init-tools-3.4-13.fc9 from koji that didn't solve the problem for me. Did you rebuild your initrd with mkinitrd? You'll need to actually have the latest version of modprobe in your initrd in order to verify this fix :) If you need a hand, let me know. Jon. No I didn't. Let me know how to do this. Confirmed fixed. No more WARNINGs from modprobe/insmod. We still get the padlock messages: padlock: VIA PadLock not detected. padlock: VIA PadLock Hash Engine not detected. But that's expected (and non-scary). Louis, updating the kernel will rebuild the initrd for you (there's a new kernel in today's rawhide as well). |