ioscan of io adapter

[Michael Murphy_2]

I have a k580 that is showing an ioscan:

bc 1 8 ccio CLAIMED BUS_NEXUS I/O Adapter
bc 2 10 ccio CLAIMED BUS_NEXUS I/O Adapter
ext_bus 0 10/0 c720 CLAIMED INTERFACE GSC built-in Fast/Wi
de SCSI Interface

At hardware address 8 it used to have lots of cards listed - fc cards, 100bt cards, etc. Do i/o adapters go bad? is there a way to force ioscan to recognize the hardware attached to it? (i saw ioscan -H enties that mention manual load of drivers) Thanks

[Patrick Wallek]

>>Do i/o adapters go bad?

Absolutely. It is possible for any electronic component to fail.

# ioscan -fnH 8

Will scan the '8' bus. If nothing shows up, then I would suspect hardware problems.

[Torsten.]

I did not see the problem so far.

Could you please post a complete

# ioscan -fn

please?


HSC expansion slots only are at path 8/... most others are at 10/...

[Mel Burslan]

Since you have not said anything about the command line switches you used with your ioscan, I need to ask if you run the command with -k or not. Try

ioscan -fn

this should query the buses for all attached hardware.

There is a good probability that the mainboard where channel 8 sits, going bad.

[Torsten.]

Compare to the attached picture.

[Torsten.]

If the expander is installed and has cards and nothing is shown in ioscan, you can even have a bad expander card.

[Matti_Kurkela]

Please see Figure 2-4 on page 28 of the Service Manual for the K-class servers:

http://ftp.parisc-linux.org/docs/platforms/A2375-90004.pdf

The hardware path 8 is the HSC I/O carrier, which can contain multiple I/O cards. The fact that multiple cards in the carrier have all failed to display would tend to indicate a problem with the carrier itself. Forcing the system to pretend the hardware is there would not be effective, because the drivers would just go into the NO_HW state.

We once had a K-class miss one of its processors. We called a HP engineer, who had seen this before - apparently the K-class may suffer from contact oxidation between the backplane and its modules. A few repeated disconnect/reconnect cycles cleaned up the connector and restored full functionality. Maybe this is something similar?

If you want to try it:
1.) Power down the server.
2.) Follow the I/O carrier removal and replacement instructions on pages 159-160 of the above-mentioned Service Manual. Repeat a few times.

MK

[Michael Murphy_2]

FYI - i am showing the adapter but none of the cards on the ioscan:

# ioscan -fnH 8
Class I H/W Path Driver S/W State H/W Type Description
============================================================
bc 1 8 ccio CLAIMED BUS_NEXUS I/O Adapter

it used to show like this:

# ioscan -fnH 8
Class I H/W Path Driver S/W State H/W Type Description
======================================================================
bc 1 8 ccio CLAIMED BUS_NEXUS I/O Adapter
ba 0 8/0 GSCtoPCI CLAIMED BUS_NEXUS GSCtoPCI Bridge
lan 0 8/0/1/0 btlan4 CLAIMED INTERFACE HP HSC 100Base-TX Prototype card
/dev/diag/lan0 /dev/ether0 /dev/lan0
lan 1 8/0/2/0 btlan4 CLAIMED INTERFACE HP HSC 100Base-TX Prototype card
/dev/diag/lan1 /dev/ether1 /dev/lan1
ba 1 8/4 GSCtoPCI CLAIMED BUS_NEXUS GSCtoPCI Bridge
lan 2 8/4/1/0 btlan4 CLAIMED INTERFACE HP HSC 100Base-TX Prototype card
/dev/diag/lan2 /dev/ether2 /dev/lan2
lan 3 8/4/2/0 btlan4 CLAIMED INTERFACE HP HSC 100Base-TX Prototype card
/dev/diag/lan3 /dev/ether3 /dev/lan3
fc 0 8/8 fcT1 CLAIMED INTERFACE HP Fibre Channel Mass Storage Adapter

[Patrick Wallek]

I would say you've got hardware failure.

Possibly this component:
ba 0 8/0 GSCtoPCI CLAIMED BUS_NEXUS GSCtoPCI Bridge

Since it and nothing below it show up.