Denis 'GNUtoo' Carikli | efd9dee | 2014-08-14 11:58:04 +0200 | [diff] [blame] | 1 | General information on boot logs |
| 2 | ================================ |
| 3 | To gather good boot logs, you must set the debug level to Spew. |
| 4 | |
| 5 | If your board uses CMOS configuration[1], you can do it like this: |
| 6 | nvramtool -w debug_level=Spew |
| 7 | |
| 8 | Else you will need to have to set the default log level at compile |
| 9 | time, to do that go in "Console --->" in make menuconfig, then set |
| 10 | "Default console log level" to SPEW |
| 11 | |
Idwer Vollering | 1918c81 | 2017-09-01 17:24:18 +0200 | [diff] [blame] | 12 | Reference: |
| 13 | ---------- |
Denis 'GNUtoo' Carikli | efd9dee | 2014-08-14 11:58:04 +0200 | [diff] [blame] | 14 | [1] in make menuconfig you should have: [*] Use CMOS for configuration values |
| 15 | This option is also known as CONFIG_USE_OPTION_TABLE in Kconfig. |
Idwer Vollering | 1918c81 | 2017-09-01 17:24:18 +0200 | [diff] [blame] | 16 | Information through SSH |
Denis 'GNUtoo' Carikli | efd9dee | 2014-08-14 11:58:04 +0200 | [diff] [blame] | 17 | ====================== |
Idwer Vollering | 1918c81 | 2017-09-01 17:24:18 +0200 | [diff] [blame] | 18 | board_status.sh can gather information through ssh with the -r |
Denis 'GNUtoo' Carikli | efd9dee | 2014-08-14 11:58:04 +0200 | [diff] [blame] | 19 | option. |
| 20 | |
| 21 | When using "-r <host>", The script will attempt to log into |
| 22 | root@<host>. |
| 23 | In order for "-r <host>" to work, the script has to be able |
| 24 | to log into the remote host's root account, without having |
| 25 | to provide a password. |
| 26 | That can be achieved with the use of SSH keys and ssh-agent. |
| 27 | |
| 28 | board_status.sh expects the remote host to have the following |
| 29 | programs in its path: cbmem, dmesg |
| 30 | |
Idwer Vollering | 1918c81 | 2017-09-01 17:24:18 +0200 | [diff] [blame] | 31 | Boot log gathering through a serial port |
Denis 'GNUtoo' Carikli | efd9dee | 2014-08-14 11:58:04 +0200 | [diff] [blame] | 32 | ======================================= |
| 33 | When using -s </dev/xxx>, board_status.sh starts by retrieving the |
Idwer Vollering | 1918c81 | 2017-09-01 17:24:18 +0200 | [diff] [blame] | 34 | boot log through the serial port. |
Denis 'GNUtoo' Carikli | efd9dee | 2014-08-14 11:58:04 +0200 | [diff] [blame] | 35 | |
| 36 | To produce such logs, power off the board, run board_status.sh |
| 37 | with the right arguments, power on the board. |
| 38 | At that point the logs will be displayed by board_status.sh as they |
| 39 | are produced by the board. |
| 40 | |
| 41 | Enter will have to be pressed once the board has booted and is in a |
| 42 | state where the script is able to log into that board. |
| 43 | |
| 44 | Publishing |
| 45 | ========== |
| 46 | The -u switch will publish the results: It will make a git patch out |
| 47 | of the status information, that will be directly pushed in the |
| 48 | board-status repository. |
| 49 | It expects the user to already have an account in coreboot's gerrit |
| 50 | instance. |