| Asset ID: |
1-72-2152050.1 |
| Update Date: | 2017-01-13 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
2152050.1
:
Incorrect baud rate causes Exadata Node to not Show System POST (Power On Self Test) , BIOS Boot Menu, nor the grub Menu During Power On.
| Related Items |
- Exadata X5-2 Hardware
- Exadata X5-8 Hardware
- Exadata X5-2 Eighth Rack
- Exadata X5-2 Full Rack
- Exadata X5-2 Quarter Rack
- Exadata X5-2 Half Rack
|
| Related Categories |
- PLA-Support>Sun Systems>x86>Engineered Systems HW>SN-x64: EXADATA
|
Created from <SR 3-12701575461>
Applies to:
Exadata X5-2 Hardware - Version All Versions to All Versions [Release All Releases]
Exadata X5-8 Hardware - Version All Versions and later
Exadata X5-2 Eighth Rack - Version All Versions and later
Exadata X5-2 Full Rack - Version All Versions and later
Exadata X5-2 Half Rack - Version All Versions and later
Information in this document applies to any platform.
Symptoms
During Exadata node power on, the system POST, the BIOS Boot menu, and the OS grub menu are not shown.
Instead, several lines of unexpected garbage (or junk) characters are shown until the OS starts.
Once the OS starts, you then see expected console message as the OS launches.
Since you cannot see the BIOS Boot Menu nor the grub menu, you are not able to easily boot into the system BIOS, nor select a different boot option, such as "CELL_USB_BOOT_CELLBOOT_usb_in_rescue_mode"
The example below shows the unexpected garbage characters.
The characters you see may be different than the ones in this example.
-> start /SYS
Are you sure you want to start /SYS(y/n)? y
/SYS started
-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y
Serial console started. To stop, type ESC (
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ << unexpected garbage characters
[big snip]
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ << unexpected garbage characters
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.39-400.276.1.el6uek.x86_64 (mockbuild@x86-ol6-builder-05) (gcc version 4.4.6 20110731 (Red Hat 4.4.6-3) (GCC) ) #1 SMP Wed Jan 27 15:36:25 PST 2016
Command line: root=/dev/md5 bootarea=c0d0 bootfrom=CELLBOOT ro loglevel=7 panic=60 debug pci=noaer log_buf_len=1m nmi_watchdog=0 nomce transparent_hugepage=never rd_NO_PLYMOUTH crashkernel=448M@128M audit=1
console=tty1 console=ttyS0,115200n8 numa=off intel_idle.max_cstate=0 processor.max_cstate=1
BIOS-provided physical RAM map:
The expected console text shown after power on is the system POST, the BIOS boot menus and the OS grub menu:
Version x.yy.zzzz. Copyright (C) 2013 American Megatrends, Inc.
BIOS Date: 11/14/2014 15:26:26 Ver: nnnnnnnn
Press F2 to run Setup (CTRL+E on Serial Console)
Press F8 for BBS POPUP (CTRL+P on Serial Console)
[snip]
BMC Firmware Revision: 3.1.2.20.g r101361
Initializing USB Controllers .. Done.
24568MB OK
USB Device(s): 1 Keyboard, 1 Mouse, 2 Hubs, 1 Storage Device
[snip]
Initializing Intel(R) Boot Agent GE v1.3.31
PXE 2.1 Build 086 (WfM 2.0)
Press Ctrl+S to enter the Setup Menu.
Booting Exadata_DBM_0: CELL_USB_BOOT_trying_C0D0_as_HD1 in 4 seconds...
Booting Exadata_DBM_0: CELL_USB_BOOT_trying_C0D0_as_HD1 in 3 seconds...
Booting Exadata_DBM_0: CELL_USB_BOOT_trying_C0D0_as_HD1 in 2 seconds...
Booting Exadata_DBM_0: CELL_USB_BOOT_trying_C0D0_as_HD1 in 1 second ...
GNU GRUB version 0.97 (613K lower / 2087424K upper memory)
***************************************************************************
* Exadata_DBM_0: CELL_USB_BOOT_trying_C0D0_as_HD1 *
* Exadata_DBM_1: CELL_USB_BOOT_trying_C0D1_as_HD1 *
* Exadata_DBM_2: CELL_USB_BOOT_trying_C0D0_as_HD2 *
* Exadata_DBM_3: CELL_USB_BOOT_trying_C0D1_as_HD2 *
* Exadata_DBM_4: CELL_USB_BOOT_trying_C0D0_as_HD3 *
* Exadata_DBM_5: CELL_USB_BOOT_trying_C0D1_as_HD3 *
* Exadata_DBM_6: CELL_USB_BOOT_trying_CELLBOOT_usb_as_final_resort *
* Exadata_DBM_7: CELL_USB_BOOT_CELLBOOT_usb_in_rescue_mode *
* *
***************************************************************************
Press any key to enter the menu
Cause
One cause of this issue is if the BIOS "Load Optimal Defaults" was selected.
This sets the /SP/serial baud rate back to the default 9600.
Solution
Take notice of the console setting in the Command line shown soon after the console does start to show output.
The example below shows this console setting: console=ttyS0,115200n8
Example:
-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y
Serial console started. To stop, type ESC (
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ [big snip] ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.39-400.276.1.el6uek.x86_64 (mockbuild@x86-ol6-builder-05) (gcc version 4.4.6 20110731 (Red Hat 4.4.6-3) (GCC) ) #1 SMP Wed Jan 27 15:36:25 PST 2016
Command line: root=/dev/md5 bootarea=c0d0 bootfrom=CELLBOOT ro loglevel=7 panic=60 debug pci=noaer log_buf_len=1m nmi_watchdog=0 nomce transparent_hugepage=never rd_NO_PLYMOUTH crashkernel=448M@128M audit=1
console=tty1 console=ttyS0,115200n8 numa=off intel_idle.max_cstate=0 processor.max_cstate=1
BIOS-provided physical RAM map:
The System BIOS and SP baud rate setting need to match the OS console setting in these three locations:
#1
In the node system BIOS.
It should be in this location:
BIOS
Advanced
Remote Access Configuration
Serial Port Mode
115200,8,n,1
Exit
Save Changes and Exit
On the node's SP:
#2
-> set /SP/serial/external pendingspeed=115200
-> set /SP/serial/external commitpending=true
#3
-> set /SP/serial/host pendingspeed=115200
-> set /SP/serial/host commitpending=true
After these changes are made, reboot the node again.
Attachments
This solution has no attachment
