1834746 Members
2481 Online
110070 Solutions
New Discussion

message in syslog

 
SOLVED
Go to solution
Javier Ortiz Guajardo
Frequent Advisor

message in syslog

I receive this message in syslog
Mux expansion bus failure detected for minor devices 0 to 63.
How can i found the cause of this message?

Thanks
The obstacles are those things that the people see when they left to see their goals.
7 REPLIES 7
Steven E. Protter
Exalted Contributor
Solution

Re: message in syslog

Could be a bad cable.
Could be a bad bus
Could be a missing terminator.

dmesg

Post the output.

Someone will decrypt it and help you. I'll be in a meeting.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Cheryl Griffin
Honored Contributor

Re: message in syslog

The messages indicate loss of communication to the HW. Could be simple as loss of power, or a cable, or something more serious such as a HW failure.
"Downtime is a Crime."
Javier Ortiz Guajardo
Frequent Advisor

Re: message in syslog

This is all i have in dmesg command (see atached file)
The obstacles are those things that the people see when they left to see their goals.
Cheryl Griffin
Honored Contributor

Re: message in syslog

Does ioscan show anything?
# ioscan -fk
"Downtime is a Crime."
Javier Ortiz Guajardo
Frequent Advisor

Re: message in syslog

i found this line in ioscan -fk
tty 1 15/2 consp1 CLAIMED INTERFACE Built-i
n Serial Port DUART
unknown -1 15/3 UNCLAIMED UNKNOWN Built-i
n Ethernet
processor 0 17 processor CLAIMED PROCESSOR Process
or

anyway here is the ioscan file
The obstacles are those things that the people see when they left to see their goals.
Massimo Bianchi
Honored Contributor

Re: message in syslog

Hi,
try running stm on the Mux, probably here is a cable problem.

Problem looks like to come and go, may be a loose connection.

HTH,
Massimo
Bill Douglass
Esteemed Contributor

Re: message in syslog

The ethernet at h/w path 15/3 does not have a driver for it configured in the kernel. That results in no s/w claiming it (leaving it in a UNCLAIMED state).

It's a bit odd, but unlikely to be related to your problem. The MUX is on a different h/w path (3/2/0).

As others have stated, it is likely a cabling issue. What devices do you have connected to the mux?