blob: c462e7de2c2ebc116ab5559771e83b7bc7b6ab9c [file] [log] [blame]
Denis 'GNUtoo' Carikliefd9dee2014-08-14 11:58:04 +02001General information on boot logs
3To gather good boot logs, you must set the debug level to Spew.
5If your board uses CMOS configuration[1], you can do it like this:
6nvramtool -w debug_level=Spew
8Else you will need to have to set the default log level at compile
9time, to do that go in "Console --->" in make menuconfig, then set
10"Default console log level" to SPEW
Idwer Vollering1918c812017-09-01 17:24:18 +020012Reference:
Denis 'GNUtoo' Carikliefd9dee2014-08-14 11:58:04 +020014[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 Vollering1918c812017-09-01 17:24:18 +020016Information through SSH
Denis 'GNUtoo' Carikliefd9dee2014-08-14 11:58:04 +020017======================
Idwer Vollering1918c812017-09-01 17:24:18 can gather information through ssh with the -r
Denis 'GNUtoo' Carikliefd9dee2014-08-14 11:58:04 +020019option.
21When using "-r <host>", The script will attempt to log into
23In order for "-r <host>" to work, the script has to be able
24to log into the remote host's root account, without having
25to provide a password.
26That can be achieved with the use of SSH keys and ssh-agent.
27 expects the remote host to have the following
29programs in its path: cbmem, dmesg
Idwer Vollering1918c812017-09-01 17:24:18 +020031Boot log gathering through a serial port
Denis 'GNUtoo' Carikliefd9dee2014-08-14 11:58:04 +020032=======================================
33When using -s </dev/xxx>, starts by retrieving the
Idwer Vollering1918c812017-09-01 17:24:18 +020034boot log through the serial port.
Denis 'GNUtoo' Carikliefd9dee2014-08-14 11:58:04 +020035
36To produce such logs, power off the board, run
37with the right arguments, power on the board.
38At that point the logs will be displayed by as they
39are produced by the board.
41Enter will have to be pressed once the board has booted and is in a
42state where the script is able to log into that board.
46The -u switch will publish the results: It will make a git patch out
47of the status information, that will be directly pushed in the
48board-status repository.
49It expects the user to already have an account in coreboot's gerrit