Sun 6800 - SC's- neither are contactable!


 
Thread Tools Search this Thread
Operating Systems Solaris Sun 6800 - SC's- neither are contactable!
# 22  
Old 04-27-2009
Quote:
Originally Posted by sbk1972
yeap, will do. Difficult job to upgrade the firmware ?
No, no biggie. Just go through the appropriate steps in the README for your upgrade and you'll be fine.
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Solaris

Application running too slow on Sun SPARC T5440 but run normal on sun M3000

Hi all, I have application running on sun server T5440 4x8x1.4 GHz, 64 GB RAM, application running very slow though load average too low. when I install my application on another server SUN M3000 (One CPU 1x8x2.5GHz, 8GB RAM), application run smoothly. Here is my server T5440 info: ... (6 Replies)
Discussion started by: insatiable1610
6 Replies

2. Solaris

d240 media tray is automatically restarting on sunfire 6800

d240 media tray(domain C) is which is connected to SUNFIRE 6800 (DOMAIN C),automatically restarting.remaining domains A and B are working fine..why i dont know..with out human intervention this domain is restarting automatically for 3 to 4 days in a day..plz solve this problem.why like this going... (4 Replies)
Discussion started by: tv.praveenkumar
4 Replies

3. Solaris

Sun Fire 280R Sun Solaris CRT/Monitor requirements

I am new to Sun. I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor? Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies

4. Solaris

Sunfire 6800 / sol 8 / scadm

Good morning all Once again, I come seeking wisdom :-) I have a sunfire 6800 with two domains. Both Sc controllers are uncontactabe, probably due to network issues, but as the server is on a different site, Im a little stuck. So, am trying to use scadm, as I know I can view / configure... (7 Replies)
Discussion started by: sbk1972
7 Replies

5. UNIX for Dummies Questions & Answers

Sun Solaris 10: How do I create a bootup disc? The Sun website confuses me

Hey there, I am starting a Computer Science Foundation year at the end of this month and am trying to get a little bit ahead of the game. I have always wanted to learn Unix and am currently struggling with creating a boot disc to run Solaris (I have chosen to study this) from as opposed to... (0 Replies)
Discussion started by: Jupiter
0 Replies

6. UNIX for Advanced & Expert Users

Help: Sun Disk partitioning for Sun V240 & StorEdge 3300

Dear Sun gurus, I have Sun Fire V240 server with its StorEdge 3300 disk-array. Following are its disks appeared in format command. I have prepared its partitions thru format and metainit & metattach (may be i have made wrong steps, causing the errors below because I have done thru some document... (1 Reply)
Discussion started by: shafeeq
1 Replies
Login or Register to Ask a Question
ddi_intr_hilevel(9F)					   Kernel Functions for Drivers 				      ddi_intr_hilevel(9F)

NAME
ddi_intr_hilevel - indicate interrupt handler type SYNOPSIS
#include <sys/ddi.h> #include <sys/sunddi.h> int ddi_intr_hilevel(dev_info_t *dip, uint_t inumber); INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). PARAMETERS
dip Pointer to dev_info structure. inumber Interrupt number. DESCRIPTION
ddi_intr_hilevel() returns non-zero if the specified interrupt is a "high level" interrupt. High level interrupts must be handled without using system services that manipulate thread or process states, because these interrupts are not blocked by the scheduler. In addition, high level interrupt handlers must take care to do a minimum of work because they are not preemptable. A typical high level interrupt handler would put data into a circular buffer and schedule a soft interrupt by calling ddi_trigger_soft- intr(). The circular buffer could be protected by using a mutex that was properly initialized for the interrupt handler. ddi_intr_hilevel() can be used before calling ddi_add_intr() to decide which type of interrupt handler should be used. Most device drivers are designed with the knowledge that the devices they support will always generate low level interrupts, however some devices, for example those using SBus or VME bus level 6 or 7 interrupts must use this test because on some machines those interrupts are high level (above the scheduler level) and on other machines they are not. RETURN VALUES
non-zero indicates a high-level interrupt. CONTEXT
These functions can be called from user or interrupt context. SEE ALSO
ddi_add_intr(9F), mutex(9F) Writing Device Drivers SunOS 5.10 7 Jan 1992 ddi_intr_hilevel(9F)