Bug 415291 - dom0 - no access to serial console
dom0 - no access to serial console
Product: Fedora
Classification: Fedora
Component: kernel-xen-2.6 (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Xen Maintainance List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-12-07 02:52 EST by Piotr Gackiewicz
Modified: 2008-06-16 22:54 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-06-16 22:54:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Piotr Gackiewicz 2007-12-07 02:52:01 EST
Description of problem:
xen is booted with:  com1=115200,8n1 console=vga,com1

after booting kernel-xen-2.6.20-2943.fc7 in dom0, mingetty lost access to
/dev/ttyS0 device: xen com1 console

Version-Release number of selected component (if applicable):
kernel-xen-2.6.20-2936.fc7 worked as expected

How reproducible:
Allways, this is permanent problem of this release

Steps to Reproduce:
1. Configure serial console access to domain0
2. Connect serial console cable
3. Use minicom on the other side
Actual results:
with kernel-xen-2.6.20-2943.fc7 mingetty logs:
Dec  7 08:39:15 xen0 /sbin/mingetty[17207]: ttyS0: not a tty
Dec  7 08:39:20 xen0 /sbin/mingetty[17208]: ttyS0: not a tty
Dec  7 08:39:25 xen0 init: Id "s" respawning too fast: disabled for 5 minutes

Expected results:
Granted access to dom0 serial console
Comment 1 Piotr Gackiewicz 2007-12-07 03:38:26 EST
strace shows:  11563 chown32("/dev/ttyS0", 0, 0)       = 0 11563 chmod("/dev/ttyS0", 0600)         = 0 11563 rt_sigaction(SIGHUP, {SIG_IGN}, {SIG_IGN}, 8) = 0 11563 open("/dev/ttyS0", O_RDWR)        = 3 11563 ioctl(3, TIOCSCTTY)               = -1 EPERM (Operation not permitted)  after that, log entry is generated: Dec  7 09:25:49 xen0 /sbin/mingetty[17443]: ttyS0: not a tty  
Comment 2 Bug Zapper 2008-05-14 11:08:13 EDT
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. 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 '7'.

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 7'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 7 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. 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. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 3 Bug Zapper 2008-06-16 22:54:51 EDT
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 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.