11-23-2006
Maybe driver error/bug on one of your pci cards,..A multi-threaded daemon processes for both the SCCP and TCAP layers that provide an interface to the respective drivers.
Log a call with Sun and send them the core dump to get analised..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have an error in my /var/adm/messages that states:
(*hostname*) inetd : fs/tcp: bind: Address already in use.
It repeats it self over and over. I have looked everywhere I can think of on the net but cant find anything. HELP Please:confused: (2 Replies)
Discussion started by: julie
2 Replies
2. Solaris
I am frequently getting following errors in /var/adm/messages. I am using solaris 8
Nov 7 16:03:03 Server Name SRS Proxy: unhandled exception: compareTimestamps format()
Nov 7 16:06:57 servername sendmail: lA2MadB5007315: to=postmaster, delay=4+22:30:07, xdelay=00:00:00, mailer=relay,... (2 Replies)
Discussion started by: sunsri01
2 Replies
3. Solaris
Hi,
I get this messages in my /var/adm/messages can you please tell me the reason for recieving this kind of messages and how to debug?
Admin 2418029 Error: Host port combo with host . Unable to resolve name
Tools 2206121 Error: ERROR.. gethostbyname() failed for errno
Admin... (3 Replies)
Discussion started by: lbreddy
3 Replies
4. Solaris
hi sirs
can u tell the difference between /var/log/syslogs and /var/adm/messages
in my working place i am having two servers.
in one servers messages file is empty and syslog file is going on increasing..
and in another servers message file is going on increasing but syslog file is... (2 Replies)
Discussion started by: tv.praveenkumar
2 Replies
5. Solaris
Hi All,
I m new to Solaris environment,
Right now I m using Solaris 10.
I get continuously following waring message in `messages` file so var partition going to full.
plz help me to stop these messages.
Feb 8 15:58:47 TSAS px: WARNING: px1: spurious interrupt from ino... (2 Replies)
Discussion started by: vikas898
2 Replies
6. UNIX for Advanced & Expert Users
The /var/adm/messages in Solaris seem to log more system messages/errors compared to /var/log/messages in Linux.
I checked the log level in Linux and they seem OK.
Is there any other log file that contains the messages or is it just that Linux doesn't log great many things? (2 Replies)
Discussion started by: gomes1333
2 Replies
7. Solaris
Hi,
Is the contents in /var/log/syslog and /var/adm/messages are same??
Regards (3 Replies)
Discussion started by: vks47
3 Replies
8. Solaris
Hi Friends,
Please help me to resove this issue ASAP.
Nov 17 16:25:52 server1 sendmail: pAH8Pnh22099: SYSERR: putoutmsg (NO-HOST): error on output channel sending "553 5.1.3 @123.com.... User address required": File too large
Nov 17 16:25:53 server1 sendmail: pAH8Pnh22099:... (1 Reply)
Discussion started by: holds_me
1 Replies
9. Emergency UNIX and Linux Support
I have Solaris-11 non-global zone running under Solaris-11 global zone. Every few minutes, this message is getting in /var/adm/message of non-global zone
Aug 31 08:31:53 zonnjc002dbp01 statd: statd: cannot talk to statd at NAS1, RPC: Timed out(5)
NAS1 is already mounted as NFS and working... (2 Replies)
Discussion started by: solaris_1977
2 Replies
10. Solaris
I had an issue with ssh on one of my servers and noticed the following
errors, listed below.
Errors in /var/adm/messagessshd lastlog_perform_login: Couln't stat /var/adm/lastlog: permission denied
sshd lastlog_openseek: /var/adm/lastlog is not a file or directory!
automountd self_check:... (0 Replies)
Discussion started by: bitlord
0 Replies
LEARN ABOUT DEBIAN
firewire
FIREWIRE(4) BSD Kernel Interfaces Manual FIREWIRE(4)
NAME
firewire -- IEEE1394 High-performance Serial Bus
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
device firewire
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
firewire_load="YES"
DESCRIPTION
FreeBSD provides machine-independent bus support and raw drivers for firewire interfaces.
The firewire driver consists of two layers: the controller and the bus layer. The controller attaches to a physical bus (like pci(4)). The
firewire bus attaches to the controller. Additional drivers can be attached to the bus.
Up to 63 devices, including the host itself, can be attached to a firewire bus. The root node is dynamically assigned with a PHY device
function. Also, the other firewire bus specific parameters, e.g., node ID, cycle master, isochronous resource manager and bus manager, are
dynamically assigned, after bus reset is initiated. On the firewire bus, every device is identified by an EUI 64 address.
FILES
/dev/fw0.0
/dev/fwmem0.0
SEE ALSO
fwe(4), fwip(4), fwohci(4), pci(4), sbp(4), eui64(5), fwcontrol(8), kldload(8), sysctl(8)
HISTORY
The firewire driver first appeared in FreeBSD 5.0.
AUTHORS
The firewire driver was written by Katsushi Kobayashi and Hidetoshi Shimokawa for the FreeBSD project.
BUGS
See fwohci(4) for security notes.
BSD
April 1, 2006 BSD