Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMasahiro Matsuya
2011-09-27 06:30:55 UTC
Created attachment 525036[details]
proposed patch
Description of problem:
A customer could not pass more than a single character to the login process.
This situation was so similar to BZ681167.
https://bugzilla.redhat.com/show_bug.cgi?id=681167
The kernel parameter includes "console=tty0 console=ttyS0,9600", and it doesn't include "rhgb quiet".
First, we tried the following upstream fixes, but this problem was not fixed.
commit 89096d735f78fab300248962030d6554f9894011
commit 74ed81c79c37c852d9011159efe1ddbdecb1fb65
commit bb3be6b60f6f0b8f8cea67b7817210b7e7164043
I checked if ply_terminal_lock() and ply_terminal_unlock() are called for what terminal with debug package. And, I found that ply_terminal_unlock() was not called clearly for /dev/ttyS0.
ply_terminal_lock() and ply_terminal_unlock() are called from ply_terminal_open() and ply_terminal_close().
ply_terminal_open()
...
-> ply_terminal_unlock, lock
ply_terminal_close()
...
-> ply_terminal_unlock()
The details plugin has add_text_display() and remove_text_display() functions and those are called when the display with a terminal is added or removed from the linked list. I noticed that add_text_display() calls ply_terminal_open().
But, remove_text_display() doesn't call ply_terminal_close(). As a result, it seems that the terminal keeps to be locked.
I created a proposed patch and confirmed it was fixed.
I will attach the patch.
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 6.1
How reproducible:
Always
Steps to Reproduce:
1. got the machine with serial console
2. boot the kernel parameter with "console=tty0 console=ttyS0,9600", and delete "rhgb quiet".
3. boot the machine, and try to login from serial console.
Actual results:
cannot login from serial console
Expected results:
can login from serial console
Comment 1Ray Strode [halfline]
2011-10-12 20:13:44 UTC
This is pretty serious (and regression from 6.0)
Comment 2Ray Strode [halfline]
2011-10-13 18:03:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2011-1766.html