Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Breaks in a table #46

Open
LSSoniX opened this issue Nov 16, 2021 · 3 comments
Open

Breaks in a table #46

LSSoniX opened this issue Nov 16, 2021 · 3 comments
Assignees

Comments

@LSSoniX
Copy link

LSSoniX commented Nov 16, 2021

Hello Plato! :)

Look at this please

MCE v1.70.0 + DB 207
Example BIOS file
https://download.asrock.com/BIOS/1700/Z690%20Taichi(1.43)ROM.zip

Command
mce.py [-ubu] -skip -exit

Result
screen

The main table is bursting with messages about new microcode. Is that how it should be now?

Thanks.

@platomav
Copy link
Owner

Hi! Do you mean that the DB is outdated?

@LSSoniX
Copy link
Author

LSSoniX commented Nov 16, 2021

No, not a DB. Displaying the table.
It just didn't happen before. In my opinion, it has always been like this - first, a complete table with all microcodes, and below the table there are messages about new microcodes.

@platomav
Copy link
Owner

platomav commented Nov 17, 2021

Ah, I see. I guess -ubu parameter does not show the input filename so that's why the confusion. This is how it actually looks (notice the "temp" files):

Capture

As you can see, the "single/temp" microcodes are different input files. This is because the initial two microcodes include "Extended Headers" so each one includes 2 microcodes basically, so 4 in total.

Capture1

MCE parses the initial 2 microcodes (first table) and IF it finds extended microcodes, it extracts them and automatically re-inputs them to parse them separately. It stores them in temp files and parses them after the initial ones. So they appear in different tables because they are different files.

@platomav platomav added the Minor label Mar 11, 2023
@platomav platomav self-assigned this Mar 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants