Bug 790839 - Unable to load module qla2xxx in 2.6.32-220.4.2.el6.i686
Summary: Unable to load module qla2xxx in 2.6.32-220.4.2.el6.i686
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.2
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-15 14:20 UTC by Werner Maes
Modified: 2013-02-14 16:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-14 16:29:42 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Werner Maes 2012-02-15 14:20:28 UTC
Description of problem:

I cannot load module qla2xxx (/lib/modules/2.6.32-220.4.2.el6.i686/kernel/drivers/scsi/qla2xxx/qla2xxx.ko) with kernel version 2.6.32-220.4.2.el6.i686. It works fine in previous kernels versions (2.6.32-220.4.1.el6.i686 for example)

Version-Release number of selected component (if applicable):


How reproducible:

modprobe qla2xxx generates:

"FATAL: Error inserting qla2xxx (/lib/modules/2.6.32-220.4.2.el6.i686/kernel/drivers/scsi/qla2xxx/qla2xxx.ko): Required key not available"

in dmesg:
ksign: module signed with unknown public key
- signature keyid: 0aab990babcb4471 ver=4
Module signed with unknown public key



Steps to Reproduce:
1. modprobe qla2xxx
  
Actual results:

module not loaded

Expected results:

module loaded

Additional info:

It also works fine on 64-bit systems.

Comment 2 RHEL Program Management 2012-05-03 05:26:24 UTC
Since RHEL 6.3 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 3 Jes Sorensen 2013-02-14 16:29:42 UTC
This has been sitting for too long with no updates - if you can reproduce
this with a recent kernel, please open a new bugzilla

Thanks


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