Sun Fire[TM] 12K/15K/E20K/E25K: Interrupt not serviced messages on System Controller

Asset ID:	1-72-1006050.1
Update Date:	2012-07-30
Keywords:

Solution Type Problem Resolution Sure

Solution 1006050.1 : Sun Fire[TM] 12K/15K/E20K/E25K: Interrupt not serviced messages on System Controller

Applies to:

Sun Fire 12K Server
Sun Fire 15K Server
Sun Fire E20K Server
Sun Fire E25K Server
All Platforms
***Checked for relevance on 20-Sep-2011***

Symptoms

The following interrupt not serviced messages may be seen on the System Controller in /var/adm/messages.

Example :

messages.3:Jun 4 14:11:18 l82ba249 unix: [ID 882636 kern.warning] WARNING: interrupt level 9 not serviced
messages.3:Jun 4 14:11:45 l82ba249 unix: [ID 882636 kern.warning] WARNING: interrupt level 12 not serviced
messages.3:Jun 4 14:11:48 l82ba249 unix: [ID 882636 kern.warning] WARNING: interrupt level 12 not serviced

Cause

The messages "interrupt level n not serviced" means an interrupt was posted, but there wasn't a device to claim it.

The error is generated when the interrupt handlers check the hardware state and decide that the hardware does not indicate an interrupt to be handled.
The standard system controller is configured for interrupt levels 6, 9, 12, and 15.

Interrupt Level	Device
4	scsi
6	network (e.g. ethernet)
6	gchip or echip
12 (hex 0xc)	ebus serial (su) driver
15 (hex 0xf)	ebus (power and i2c)

Solution

As of this writing, "not serviced" messages for interrupts 4 and 15 have not been seen in any system message files on Sun Fire[TM] 12K/15K/E20K/E25K system controllers.

Interrupt level 6 (network) error has been addressed by the driver patches 110723-06 for Solaris[TM] 5.8 and 112965-02 for Solaris[TM] 5.9.

Interrupt level 9 (gchip) error is fixed with patches for SMS 1.2 and 1.3 and Solaris 8 and 9:

114531-02 SSC 1.2: echip/gchip/consbus Patch for Solaris 8
114532-02 SSC 1.2.1: echip/gchip/consbus Patch for Solaris 9
114627-04 SSC 1.3: echip scman patch for Solaris 8
116000-01 SSC 1.3.1: number of interrupt level 9 messages fixed

Interrupt level 12 (Serial connection) errors are noticed often. You may look at the console log or /var/adm/messages to see any messages reported with the serial line connection. It has been seen in the past that unterminated cables attached to the external serial connection on an SC have caused high numbers of these interrupt messages to be logged, the cable possibly acting as an aerial with EMI/RF interference, so check if these exist and if so disconnect them.
Also check the 5.8 su patch on the SCs is 109793-15 or higher as this fixes CR 4399541.

No action is required as these messages are not a cause of any failures.
You may check the other errors in messages file to see if there is problem on the bus or network. In the current system controller with the standard configuration, these errors can be ignored.

It is highly recommend to upgrade to the latest SMS version 1.6 and Solaris 9 or 10 to benefit from the implemented bug fixes and enhancements.

Interrupt level 9 (gchip) error is reported in CR 4725348. See this bug for additional information.

Please report to TSC referencing this doc if you see any errors pointing to interrupt level 15.

12K/15K, /var/adm/messages, system controller, interrupt
Previously Published As
48185

Change History
Reviewed by ESG Content Team on 24 Nov, 2009.
Date: 2009-11-24
User Name: 71349
Action: Small formatting changes.
Added keyword interrupt.
Changed PTS to TSC

Attachments

This solution has no attachment