?
Solved

console messages

Posted on 1998-06-11
2
Medium Priority
?
683 Views
Last Modified: 2013-12-27
Hi
I noticed some console messages I am unfamiliar with, can anyone tell me anything about them?
Platform is Solaris 2.5 running on Sparc 2.
Didn't suffer any ill effects as far as I know -- Just curious.

Console Messages:

TIOCFLUSH: Timer expired
ttysw - TIOCSWINS2: Timer expired


NOTICE: zs3:ring buffer overflow
0
Comment
Question by:gormenghast
[X]
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 Comments
 
LVL 4

Accepted Solution

by:
jlms earned 300 total points
ID: 2007971
From the Solaris 2.6 answerbook (should apply to your situation):


zsnumber: silo overflow

    Cause:

This message means that the Zilog 8530 character input silo (or serial port FIFO) overflowed before it
    could be serviced. The zs(4S) driver, which talks to a Zilog Z8530 chip, is reporting that the FIFO (holding
    about two characters) has been overrun. The number after zs shows which serial port experienced an
    overflow:

        zs0 - tty serial port 0 (/dev/ttya)
        zs1 - tty serial port 1 (/dev/ttyb)
        zs2 - keyboard port (/dev/kbd)
        zs3 - mouse port (/dev/mouse)

    Action:

Silo overflows indicate that data in the respective serial port FIFO has been lost. However, consequences
    of silo overflows might be negligible if the overflows occur infrequently, if data loss is not catastrophic, or if
    data can be recovered or reproduced. For example, although a silo overflow on the mouse driver (zs3)
    indicates that the system could not process mouse events quickly enough, the user can perform mouse motions
    again. Similarly, lost data from a silo overflow on a serial port with a modem connection transferring data using
    uucp(1C) will be recovered when uucp discovers the loss of data and requests retransmission of the corrupted
    packet.

    Frequent silo overflow messages can indicate a zs hardware FIFO problem, a serial driver software problem, or
    abnormal data or system activity. For example, the system ignores interrupts during system panics, so mouse
    and keyboard activity result in silo overflows.

    If the serial ports experiencing silo overflows are not being used, a silo overflow could indicate the onset of a
    hardware problem.

    Technical Notes Another type of silo overflow is one that occurs during reboot when an HDLC line is connected
    to any of the terminal ports. For example, an X.25 network could be sending frames before the kernel has been
    told to expect them. Such overflow messages can be ignored.


The other two messages are related to arcane network stuff, so maybe your network (is it an X.25 network?) is having problems high use.


0
 
LVL 2

Author Comment

by:gormenghast
ID: 2007972
Thanks!
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

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

When you do backups in the Solaris Operating System, the file system must be inactive. Otherwise, the output may be inconsistent. A file system is inactive when it's unmounted or it's write-locked by the operating system. Although the fssnap utility…
Every server (virtual or physical) needs a console: and the console can be provided through hardware directly connected, software for remote connections, local connections, through a KVM, etc. This document explains the different types of consol…
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

801 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