Bug 172785 - can't login on console,tty1,tty2 etc after kernel upgrade
Summary: can't login on console,tty1,tty2 etc after kernel upgrade
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel
Version: 3.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Peter Martuccelli
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-11-09 18:53 UTC by Normand Labossiere
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-19 18:51:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Normand Labossiere 2005-11-09 18:53:09 UTC
Description of problem:can't login on console,tty1,tty2 etc after kernel 
upgrade 2.4.21-20 > 2.4.21-27.0.2  message found in /var/log/messages: > 
login : module unknown

but i can login with ssh 


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


How reproducible:


Steps to Reproduce:
1.rpm -U kernel-2.4.21-27.0.2.ia32e.rpm
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Ernie Petrides 2005-11-15 00:21:41 UTC
Hello, Normand.  Which module is unknown?  (It seems like part of
the error message was not included.)

Please also include the output of "lsmod" and indicate whether you
were previously relying on any modules from the kernel-unsupported RPM.

Thanks in advance.


Comment 2 Red Hat Bugzilla 2007-03-18 22:35:23 UTC
User jparadis's account has been closed

Comment 3 RHEL Program Management 2007-10-19 18:51:24 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.


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