[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference mvblab::sable

Title:SABLE SYSTEM PUBLIC DISCUSSION
Moderator:COSMIC::PETERSON
Created:Mon Jan 11 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2614
Total number of notes:10244

2502.0. "IP interrupt CPU on "shutdown -r"" by PANTER::MARTIN (Be vigilant...) Mon Jan 27 1997 08:59

    A customer reported a problem with the Unix "shutdown -r"
    on his SMP sable machine.
    
    Everytime he uses the "shutdown -r" command, the system
    shuts down properly, but the system does't reboot automatically.
    
    At the console the system just keep on printing
    "IP interrupt CPU 0", halting it with the halt button
    doesn't help, only the restart or power cycle cure
    this...
    
    we asked the customer to upgrade his system's FW to
    v4.7 but this didn't help.
    
    This is an EV4.5 (4/275) with 4 CPUs at the following revs:
    
                    Firmware : V4.7 (From CD v3.8)
                               CPU0 B2040-AB  Rev B01   SW 34
                               CPU1 B2040-AB  Rev B01   SW 37
                               CPU2 B2040-AB  Rev B01   SW 37
                               CPU3 B2040-AB  Rev B01   SW 37
    
    
    Has it to do with the SW rev 34 of the 1st CPU (CPU0) ???
    
    Feedback will be welcomed, the only idea I have left for
    this is to replace the CPU 0 (rev SW 34), but we'll have 
    to plan the intervention outside normal working hours
    (week-end probably) and I'd prefer to go straight to the
    correct solution...
    
    Cheers,
    
    					============================
    					Alain MARTIN/SSG Switzerland
T.RTitleUserPersonal
Name
DateLines
2502.1Something to tryAFW3::MAZURTue Jan 28 1997 13:0425
The message "IP interrupt on CPU 0" is printed by the console.  The console
just dismisses the interrupt. 

Suspecting broken hardware, from console mode, a deposit can be done
to cause an IP interrupt.  You should see one message.  If you see the
continuous stream of "IP interrupt on CPU 0" messages, then you have
broken hardware.

With an EV4 
------------------------
>>> d -p -q 38x000160 1                (set bit 1)
              |
              |
              +-------- 0 or 1 or 2 or 3 to select which CPU


Sample log:
--------------
P00>>>d -p -q 380000160 1
IP interrupt on CPU 0
P00>>>