Bug 594721

Summary:	modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.32-27.el6.x86_64/kernel/drivers/crypto/padlock-sha.ko): No such device
Product:	Red Hat Enterprise Linux 6	Reporter:	Michal Haško <mhasko>
Component:	kernel	Assignee:	Red Hat Kernel Manager <kernel-mgr>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0	CC:	Jes.Sorensen, pslavice, twaugh
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-28 10:29:01 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:	846704

Description Michal Haško 2010-05-21 13:03:39 UTC

Description of problem:
I get this error during boot after entering my LUKS password for a partition.
modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.32-27.el6.x86_64/kernel/drivers/crypto/padlock-sha.ko): No such device

Version-Release number of selected component (if applicable):
kernel-2.6.32-27.el6.x86_64

How reproducible:
100%

Comment 1 RHEL Program Management 2010-05-21 13:16:16 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 2 RHEL Program Management 2010-07-15 14:38:45 UTC

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 3 RHEL Program Management 2011-10-07 15:03:45 UTC

Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 4 Jes Sorensen 2013-02-27 18:06:40 UTC

Is this still a problem?

The padlock driver is only used on VIA based systems. Is this a VIA system
or was the disk moved from one system to another?

Comment 5 Jes Sorensen 2013-02-27 18:08:35 UTC

*** Bug 589042 has been marked as a duplicate of this bug. ***

Comment 6 Michal Haško 2013-02-28 10:19:39 UTC

(In reply to comment #4)
> Is this still a problem?

My machine was reinstalled countless of times since I reported this issue.
Currently (on RHEL6.4), there is no longer such problem.

Comment 7 Jes Sorensen 2013-02-28 10:29:01 UTC

Thanks for the update - closing