diff options
| author | Andrew Jeffery <andrew@aj.id.au> | 2019-03-25 18:15:58 +1030 |
|---|---|---|
| committer | oohal <oohal@users.noreply.github.com> | 2019-05-09 17:04:30 +1000 |
| commit | f8f9d5ece92da8da5d7331a6e4c924e2f485cc81 (patch) | |
| tree | 3a75fc6950f70c636e5cb93ad1eaa7925d460a87 /CONTRIBUTING.md | |
| parent | 749ce5cf1916af326ef46fad6d79cf52dd252a6f (diff) | |
| download | skiboot-f8f9d5ece92da8da5d7331a6e4c924e2f485cc81.zip skiboot-f8f9d5ece92da8da5d7331a6e4c924e2f485cc81.tar.gz skiboot-f8f9d5ece92da8da5d7331a6e4c924e2f485cc81.tar.bz2 | |
core/flash: Retry requests as necessary in flash_load_resource()
[ Upstream commit cccf5d79de07844cf095b8f45146b92944d15c2e ]
We would like to successfully boot if we have a dependency on the BMC
for flash even if the BMC is not current ready to service flash
requests. On the assumption that it will become ready, retry for several
minutes to cover a BMC reboot cycle and *eventually* rather than
*immediately* crash out with:
[ 269.549748] reboot: Restarting system
[ 390.297462587,5] OPAL: Reboot request...
[ 390.297737995,5] RESET: Initiating fast reboot 1...
[ 391.074707590,5] Clearing unused memory:
[ 391.075198880,5] PCI: Clearing all devices...
[ 391.075201618,7] Clearing region 201ffe000000-201fff800000
[ 391.086235699,5] PCI: Resetting PHBs and training links...
[ 391.254089525,3] FFS: Error 17 reading flash header
[ 391.254159668,3] FLASH: Can't open ffs handle: 17
[ 392.307245135,5] PCI: Probing slots...
[ 392.363723191,5] PCI Summary:
...
[ 393.423255262,5] OCC: All Chip Rdy after 0 ms
[ 393.453092828,5] INIT: Starting kernel at 0x20000000, fdt at
0x30800a88 390645 bytes
[ 393.453202605,0] FATAL: Kernel is zeros, can't execute!
[ 393.453247064,0] Assert fail: core/init.c:593:0
[ 393.453289682,0] Aborting!
CPU 0040 Backtrace:
S: 0000000031e03ca0 R: 000000003001af60 ._abort+0x4c
S: 0000000031e03d20 R: 000000003001afdc .assert_fail+0x34
S: 0000000031e03da0 R: 00000000300146d8 .load_and_boot_kernel+0xb30
S: 0000000031e03e70 R: 0000000030026cf0 .fast_reboot_entry+0x39c
S: 0000000031e03f00 R: 0000000030002a4c fast_reset_entry+0x2c
--- OPAL boot ---
The OPAL flash API hooks directly into the blocklevel layer, so there's
no delay for e.g. the host kernel, just for asynchronously loaded
resources during boot.
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Signed-off-by: Stewart Smith <stewart@linux.ibm.com>
Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
Diffstat (limited to 'CONTRIBUTING.md')
0 files changed, 0 insertions, 0 deletions