Komemiute wrote:
While on the L1 display I get "1.5V Low warningh limit reached
There's not very much information in your post to work with, but I'd suspect that 1.5V low warning is probably going to end up being the Titanic end of the iceberg.
You didn't mention which log you saw the message in (an IRIX generated log or one from the L1/L2/PROM/POD?), but just to cover all of the bases I'd suggest connecting a
3800, 8, N, 1 serial terminal (via
null modem cable) to the L1/console port on the problem brick so you can examine the power-on diagnostic messages.
When you set up the serial terminal program, set a very large scroll-back buffer (at least 5k lines) so you can capture the entire session. Before you close the serial terminal program, be sure to save the session as a text file.
The initial serial terminal connection with the console port will be with the level 1 (L1) controller (the L1 is running anytime power is connected to the brick). Before you power up the system run the "log" command at the L1 command prompt and capture the output. Then power up the system and Immediately press the "d" and "control" keys (on the serial terminal) simultaneously to switch you from L1 mode to console mode. The output of the power-on diagnostics session should scroll across the serial terminal window. If the problem brick powers itself down shortly after you've powered it up, repeat the power up process without switching to console mode and run "env" against the L1 as soon as the brick is powered up.
If the problem brick does remain powered through the diagnostics session, execute a "control t" keypress to switch back to L1 mode. Once you're there (with the brick powered up and running), capture the output of the L1 "log" and "env" commands.
While you still have the serial terminal configured, move your serial cable to the 'console' port on the Level 2 (L2) controller, and run/capture the output of the L2 "log" and "env" commands.
Post the captured data here (you can trim the text to include just the pertinent bits) along with an "hinv -vm" (for the entire system).
Login
Register
FAQ
Search
