Hide Forgot
Description of problem: kernel 4.4.4-200 denies console input coming from hvc0 when running in paravirtualised mode on a xen server i.e. Citrix. I assume, it gets caused by "/etc/securetty" being deleted while updating something. Version-Release number of selected component (if applicable): 4.4.4-200 PAE How reproducible: 100% Steps to Reproduce: 1. setup a xenserver 2. start a vm with that kernel 3. console does not take any input Actual results: /etc/securetty got deleted Expected results: do not touch it, if you do not know, which kind of environment your running in. Additional info:
The kernel doesn't do anything with the /etc/securetty. If something deleted it, it was done in userspace.
I don't see anything off hand that owns or creates this file, so I would expect once you put it in place it should stay there. Can you identify all the packages that were updated when the file disappeared?
unfurtunatly those are productive servers, you do not check this until you need it and than it's too late :) Maybe this observation helps you: i freshly installed a FC23 on one of those serverimages. Without a /etc/securetty file, i could enter into the console, but it took 5-10 minutes after the system booted. As i wrote this bugreport, i could not enter into a console for Kernel 4.4.4 BUT NOW .. a fews days later, it works, even without a /etc/securetty file. O== Something else seems to cause the console input bug after a reboot. ==O Whatever it is, it's nasty, as you normally do not reboot a server without a reason, and afterwards you wanne/must check things. Impossible if the network card isn't working. Which reminds of another unsolved network problem. But that another bugreport.
So, this sounds to me like systemd isn't starting the getty on that console as it should (it's taking 5-10min to start instead of starting right away). (see: http://0pointer.de/blog/projects/serial-console.html ) Moving over to systemd folks for further debugging/comment...
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.