Bug 477868 - pts output lock
pts output lock
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-12-24 10:03 EST by Need Real Name
Modified: 2009-12-18 02:23 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 02:23:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
dmesg output (42.61 KB, text/plain)
2008-12-24 10:03 EST, Need Real Name
no flags Details
ps output (10.12 KB, text/plain)
2008-12-24 10:04 EST, Need Real Name
no flags Details
lspci (17.98 KB, text/plain)
2008-12-24 10:05 EST, Need Real Name
no flags Details
sensors (2.82 KB, text/plain)
2008-12-24 10:05 EST, Need Real Name
no flags Details

  None (edit)
Description Need Real Name 2008-12-24 10:03:44 EST
Created attachment 327814 [details]
dmesg output

At some point the 
Linux cnasdaq #1 SMP Mon Dec 1 22:21:35 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
gets in a strange state it cannot print anything longer than about 200 bytes to terminal.

Problem description:
Remotely login via ssh.
stops after about 200 bytes output. pts is locked, no Ctl-C or anything.

login again and run dmesg 
dmesg >/tmp/st_dmesg.txt 2>&1&

executed OK, because no long output printed.

This happend relatively seldomly. after a reboot - everything 
is OK, the computer can print long output once again.

Looks like some kind pts race in kernel
Comment 1 Need Real Name 2008-12-24 10:04:51 EST
Created attachment 327815 [details]
ps output
Comment 2 Need Real Name 2008-12-24 10:05:21 EST
Created attachment 327816 [details]
Comment 3 Need Real Name 2008-12-24 10:05:51 EST
Created attachment 327817 [details]
Comment 4 Bug Zapper 2009-11-18 05:33:34 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 5 Bug Zapper 2009-12-18 02:23:24 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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