Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17


serial port problem

Posted on 1999-09-07
Medium Priority
Last Modified: 2011-10-03
I am getting the following message when I am at the consile:
"S1: respawning too fast, disbled for 5 minutes" What is the problem ? (I am using Slackware 4)
and how do I solve it?
Question by:ghmklaas
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2

Expert Comment

ID: 2026933
Could you post your /etc/inittab file here please?

It looks like there is a line in that file that isn't quite right.

Accepted Solution

Loren earned 200 total points
ID: 2030702
As mnw21 said, looking at the inittab would be useful, but I'm fairly sure of what the jist of the problem is as I have seen similar problems before.  It sounds like your inittab entry with the id of 'S1' (the 2 character identifier before the first colon on a line) which has been told to respawn (when it dies: usually used for getty) is dying very quickly and causing very rapid and repetitive respawns.  Such short-lived getty processes are almost always caused by an error during startup, either because of a hardware problem, a system configuration problem, or some other little quirk.  'init' is trying to save you a headache by pausing the respawn for a few minutes, so as to not suck up 100% of CPU time while giving you (the admin) a chance to fix the problem.  By the id of the inittab entry I'm guessing it's the getty process for either /dev/ttyS0 or /dev/ttyS1.  Most often you should not need getty running on your serial ports unless you 1) have a dumb terminal pulged into it and plan to log in from there, or 2) have a modem (in answer mode) there and plan on dialing in via modem.  In most other cases the S1 entry can be commented out by preceding it with a hash sign '#'.

Hope that helps.

Expert Comment

ID: 2030718
Sounds like a reasonable analysis, and a very good explanation.

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I. Introduction There's an interesting discussion going on now in an Experts Exchange Group — Attachments with no extension ( This reminded me of questions tha…
It’s 2016. Password authentication should be dead — or at least close to dying. But, unfortunately, it has not traversed Quagga stage yet. Using password authentication is like laundering hotel guest linens with a washboard — it’s Passé.
Learn several ways to interact with files and get file information from the bash shell. ls lists the contents of a directory: Using the -a flag displays hidden files: Using the -l flag formats the output in a long list: The file command gives us mor…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Suggested Courses

664 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question