cbmem.log for kaisa
is there any way to fix slow boot on these devices it took 2-4 mins to boot i have here cbmem.log for you to check
cbmem.log for kaisa
is there any way to fix slow boot on these devices it took 2-4 mins to boot i have here cbmem.log for you to check
cbmem.log for duffy
log says it thinks it needs to redo RAM training even though the memory hasn’t changed, very odd
I though the 2-4 mins boot is normal cuz i have 1 kaisa and 3 duffy chromebox until i researched so what do you think here is the problem
that’s way too long, ram training on DDR4 shouldn’t take more than 2-3s per GB installed.
please provide the output of cbmem -t as well.
I have a WYVERN box here and no such issues
48 entries total:
0:1st timestamp 9,471 (0)
11:start of bootblock 15,706 (6,235)
12:end of bootblock 19,711 (4,005)
13:starting to load romstage 19,712 (0)
14:finished loading romstage 20,257 (545)
1:start of romstage 20,730 (473)
970:loading FSP-M 27,548 (6,817)
2:before RAM initialization 27,900 (352)
950:calling FspMemoryInit 40,597 (12,696)
951:returning from FspMemoryInit 85,901 (45,304)
550:starting to load ChromeOS VPD 86,530 (629)
551:finished loading ChromeOS VPD (RO) 86,633 (102)
3:after RAM initialization 87,473 (839)
948:starting CSE firmware sync 87,473 (0)
949:finished CSE firmware sync 95,491 (8,017)
4:end of romstage 106,777 (11,285)
100:start of postcar 110,665 (3,888)
101:end of postcar 110,666 (0)
8:starting to load ramstage 110,669 (3)
15:starting LZMA decompress (ignore for x86) 110,678 (9)
16:finished LZMA decompress (ignore for x86) 136,504 (25,826)
9:finished loading ramstage 136,630 (125)
10:start of ramstage 139,092 (2,461)
971:loading FSP-S 139,270 (178)
15:starting LZMA decompress (ignore for x86) 139,275 (4)
16:finished LZMA decompress (ignore for x86) 174,407 (35,131)
30:device enumeration 186,153 (11,746)
954:calling FspSiliconInit 198,700 (12,547)
955:returning from FspSiliconInit 254,495 (55,794)
31: 254,789 (293)
40:device configuration 261,601 (6,812)
956:calling FspNotify(AfterPciEnumeration) 264,256 (2,655)
957:returning from FspNotify(AfterPciEnumeration) 264,513 (256)
50:device enable 265,429 (916)
60:device initialization 265,812 (383)
15:starting LZMA decompress (ignore for x86) 272,482 (6,669)
16:finished LZMA decompress (ignore for x86) 272,737 (254)
70:device setup done 333,401 (60,664)
75:cbmem post 333,411 (10)
80:write tables 333,506 (94)
85:finalize chips 340,440 (6,933)
90:starting to load payload 340,455 (15)
15:starting LZMA decompress (ignore for x86) 340,545 (90)
16:finished LZMA decompress (ignore for x86) 609,527 (268,982)
958:calling FspNotify(ReadyToBoot) 609,594 (66)
959:returning from FspNotify(ReadyToBoot) 612,378 (2,784)
960:calling FspNotify(EndOfFirmware) 612,379 (0)
961:returning from FspNotify(EndOfFirmware) 612,596 (217)
99:selfboot jump 612,795 (199)
Total Time: 603,303
48 entries total:
0:1st timestamp 9,544 (0)
11:start of bootblock 15,915 (6,371)
12:end of bootblock 19,918 (4,002)
13:starting to load romstage 19,918 (0)
14:finished loading romstage 20,464 (545)
1:start of romstage 20,938 (473)
970:loading FSP-M 26,960 (6,022)
2:before RAM initialization 27,313 (353)
950:calling FspMemoryInit 40,331 (13,017)
951:returning from FspMemoryInit 19,868,718 (19,828,387)
550:starting to load ChromeOS VPD 19,869,363 (644)
551:finished loading ChromeOS VPD (RO) 19,869,522 (159)
3:after RAM initialization 19,883,905 (14,382)
948:starting CSE firmware sync 19,883,905 (0)
949:finished CSE firmware sync 19,886,458 (2,552)
4:end of romstage 19,898,714 (12,256)
100:start of postcar 19,901,611 (2,897)
101:end of postcar 19,901,611 (0)
8:starting to load ramstage 19,901,614 (2)
15:starting LZMA decompress (ignore for x86) 19,901,637 (23)
16:finished LZMA decompress (ignore for x86) 19,927,456 (25,818)
9:finished loading ramstage 19,927,674 (218)
10:start of ramstage 19,929,455 (1,781)
971:loading FSP-S 19,929,528 (72)
15:starting LZMA decompress (ignore for x86) 19,929,533 (4)
16:finished LZMA decompress (ignore for x86) 19,964,467 (34,934)
30:device enumeration 19,976,341 (11,873)
15:starting LZMA decompress (ignore for x86) 19,985,411 (9,070)
16:finished LZMA decompress (ignore for x86) 19,985,653 (241)
954:calling FspSiliconInit 19,989,375 (3,722)
955:returning from FspSiliconInit 20,699,485 (710,109)
31: 20,699,780 (294)
40:device configuration 20,706,254 (6,473)
956:calling FspNotify(AfterPciEnumeration) 20,708,890 (2,636)
957:returning from FspNotify(AfterPciEnumeration) 20,709,090 (199)
50:device enable 20,710,093 (1,003)
60:device initialization 20,710,468 (375)
70:device setup done 20,810,460 (99,991)
75:cbmem post 20,810,470 (10)
80:write tables 20,810,565 (94)
85:finalize chips 20,817,089 (6,524)
90:starting to load payload 20,817,104 (14)
15:starting LZMA decompress (ignore for x86) 20,817,195 (90)
16:finished LZMA decompress (ignore for x86) 21,080,673 (263,478)
958:calling FspNotify(ReadyToBoot) 21,080,744 (70)
959:returning from FspNotify(ReadyToBoot) 21,083,499 (2,755)
960:calling FspNotify(EndOfFirmware) 21,083,499 (0)
961:returning from FspNotify(EndOfFirmware) 21,083,769 (269)
99:selfboot jump 21,083,973 (204)
Total Time: 21,074,406
use an unformatted code block - 3 backticks
and how do i do that
I just told you. You can also search for ‘Discourse unformatted code block’
48 entries total:
0:1st timestamp 9,471 (0)
11:start of bootblock 15,706 (6,235)
12:end of bootblock 19,711 (4,005)
13:starting to load romstage 19,712 (0)
14:finished loading romstage 20,257 (545)
1:start of romstage 20,730 (473)
970:loading FSP-M 27,548 (6,817)
2:before RAM initialization 27,900 (352)
950:calling FspMemoryInit 40,597 (12,696)
951:returning from FspMemoryInit 85,901 (45,304)
550:starting to load ChromeOS VPD 86,530 (629)
551:finished loading ChromeOS VPD (RO) 86,633 (102)
3:after RAM initialization 87,473 (839)
948:starting CSE firmware sync 87,473 (0)
949:finished CSE firmware sync 95,491 (8,017)
4:end of romstage 106,777 (11,285)
100:start of postcar 110,665 (3,888)
101:end of postcar 110,666 (0)
8:starting to load ramstage 110,669 (3)
15:starting LZMA decompress (ignore for x86) 110,678 (9)
16:finished LZMA decompress (ignore for x86) 136,504 (25,826)
9:finished loading ramstage 136,630 (125)
10:start of ramstage 139,092 (2,461)
971:loading FSP-S 139,270 (178)
15:starting LZMA decompress (ignore for x86) 139,275 (4)
16:finished LZMA decompress (ignore for x86) 174,407 (35,131)
30:device enumeration 186,153 (11,746)
954:calling FspSiliconInit 198,700 (12,547)
955:returning from FspSiliconInit 254,495 (55,794)
31: 254,789 (293)
40:device configuration 261,601 (6,812)
956:calling FspNotify(AfterPciEnumeration) 264,256 (2,655)
957:returning from FspNotify(AfterPciEnumeration) 264,513 (256)
50:device enable 265,429 (916)
60:device initialization 265,812 (383)
15:starting LZMA decompress (ignore for x86) 272,482 (6,669)
16:finished LZMA decompress (ignore for x86) 272,737 (254)
70:device setup done 333,401 (60,664)
75:cbmem post 333,411 (10)
80:write tables 333,506 (94)
85:finalize chips 340,440 (6,933)
90:starting to load payload 340,455 (15)
15:starting LZMA decompress (ignore for x86) 340,545 (90)
16:finished LZMA decompress (ignore for x86) 609,527 (268,982)
958:calling FspNotify(ReadyToBoot) 609,594 (66)
959:returning from FspNotify(ReadyToBoot) 612,378 (2,784)
960:calling FspNotify(EndOfFirmware) 612,379 (0)
961:returning from FspNotify(EndOfFirmware) 612,596 (217)
99:selfboot jump 612,795 (199)
Total Time: 603,303
here is the more neatly version
ama be honest im in kind of a lost rn
what do i do next
you’re lost about how to format text on a forum post?
that boot log shows your boot time was 600ms
o that because i rebooted its actually fast when u reboot other than power off and switch on
48 entries total:
0:1st timestamp 9,628 (0)
11:start of bootblock 16,669 (7,040)
12:end of bootblock 21,084 (4,415)
13:starting to load romstage 21,084 (0)
14:finished loading romstage 21,634 (550)
1:start of romstage 22,114 (479)
970:loading FSP-M 29,248 (7,133)
2:before RAM initialization 29,597 (349)
950:calling FspMemoryInit 42,778 (13,180)
951:returning from FspMemoryInit 87,500 (44,721)
550:starting to load ChromeOS VPD 88,138 (637)
551:finished loading ChromeOS VPD (RO) 88,242 (104)
3:after RAM initialization 89,101 (859)
948:starting CSE firmware sync 89,101 (0)
949:finished CSE firmware sync 97,128 (8,026)
4:end of romstage 108,527 (11,398)
100:start of postcar 112,482 (3,955)
101:end of postcar 112,483 (0)
8:starting to load ramstage 112,485 (2)
15:starting LZMA decompress (ignore for x86) 112,527 (41)
16:finished LZMA decompress (ignore for x86) 138,394 (25,867)
9:finished loading ramstage 138,520 (125)
10:start of ramstage 141,085 (2,564)
971:loading FSP-S 141,165 (80)
15:starting LZMA decompress (ignore for x86) 141,170 (4)
16:finished LZMA decompress (ignore for x86) 176,554 (35,384)
30:device enumeration 188,364 (11,809)
954:calling FspSiliconInit 3,211,130 (3,022,765)
955:returning from FspSiliconInit 3,259,628 (48,498)
31: 3,259,923 (294)
40:device configuration 3,266,795 (6,871)
956:calling FspNotify(AfterPciEnumeration) 3,269,563 (2,768)
957:returning from FspNotify(AfterPciEnumeration) 3,269,767 (204)
50:device enable 3,270,753 (985)
60:device initialization 3,271,137 (384)
15:starting LZMA decompress (ignore for x86) 3,273,732 (2,594)
16:finished LZMA decompress (ignore for x86) 3,273,997 (265)
70:device setup done 3,373,441 (99,444)
75:cbmem post 3,373,452 (10)
80:write tables 3,373,546 (94)
85:finalize chips 3,379,862 (6,315)
90:starting to load payload 3,379,877 (15)
15:starting LZMA decompress (ignore for x86) 3,379,968 (90)
16:finished LZMA decompress (ignore for x86) 3,648,926 (268,958)
958:calling FspNotify(ReadyToBoot) 3,648,997 (70)
959:returning from FspNotify(ReadyToBoot) 3,651,734 (2,737)
960:calling FspNotify(EndOfFirmware) 3,651,734 (0)
961:returning from FspNotify(EndOfFirmware) 3,651,951 (217)
99:selfboot jump 3,652,151 (199)
Total Time: 3,642,499
here is the shutdown boot
to be honest this is my first time asking for help
hmm, 3s+ for FspSiliconInit isn’t right
my boot delay is coming from FSP-M (MemoryInit) how do i speed it up?
you can’t.
need to figure out why it’s wanting to redo RAM training when the dimms haven’t changed
any more ideas or test should i do?