1 General information on boot logs
2 ================================
3 To gather good boot logs, you must set the debug level to Spew.
5 If your board uses CMOS configuration[1], you can do it like this:
6 nvramtool -w debug_level=Spew
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
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.
16 Information through SSH
17 ======================
18 board_status.sh can gather information through ssh with the -r
21 When using "-r <host>", The script will attempt to log into
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.
28 board_status.sh expects the remote host to have the following
29 programs in its path: cbmem, dmesg
31 Boot log gathering through a serial port
32 =======================================
33 When using -s </dev/xxx>, board_status.sh starts by retrieving the
34 boot log through the serial port.
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.
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.
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