[solved] Some Question dmesg warning

[Spinnifex]

Hello

On Startup I get this warning:

Code: Select all

tpm_tis MSFT0101:00: IRQ index 0 not found


How do I handle that?

Regards,

Spinnifex

[doktor5000]

Why do you think that you need to handle that ?

[jiml8]

It is best handled by ignoring it, unless there is some related malfunction in your system. Which probably is not the case.

[Spinnifex]

Why do you think that you need to handle that ?

Two reasons

1. If I read something like "not found" on a startup message I get the impression that something is not as it should be
2. If I did not change something I know I changed and after reboot such a message appear I also feel nervous

Maybe I changed something. Since I am not able to study every aspect of startup messages etc. I post this question.

Meanwhile I googled a bit for "tpm_tis" didn't found much. Maybe a mainboard feature I disabled!?

What I want is a stable system where I know why messages like those appear.

Thanks much.

Spinnifex

[doktor5000]

What I want is a stable system where I know why messages like those appear.

So you assume your system is now unstable since you get that message ? Easy fix is to not look at dmesg output, then your system will be stable again.

[Spinnifex]

If you think thats funny. No is not.

I just want to know why this appear when this previously did not.

[jiml8]

If you want to get rid of all warning messages you will need to compile a custom kernel that is tailored for your specific hardware, as a beginning. You might need to do the same thing for many of the major libraries in the system. At a minimum, you will have to recompile them with compiler flags set that specify the exact target architecture.

Good luck with that. It is not easy and, when upgrade time comes, you won't be able to.

The kernel in this, and in every other, distribution is designed to be somewhat generic and to start up on many different architectures based upon the i586 or x86-64 standard. This means that during the early startup, the system spends time polling the hardware to find what is actually present. But the number of variations and permutations of what COULD be present are simply huge. For instance, is this southbridge chip a Rev.1? Or a Rev.2? A lot of times, the easiest way to tell is just to try to enable this specific function. If it enables, we have a Rev.1; if it doesn't enable, we have a Rev.2. So an attempt is made to enable it. Attempt fails; warning message is issued, and the system proceeds without depending on that function.

Now scale this to encompass all the chips in the system, and you will see warning messages are not at all uncommon. Why not suppress those messages? Because someone out there might need the R.1 version and not the R.2 version for his specific requirements, and this is his clue about what he has. Many programs will read the dmesg output to figure such things out; I myself have written code in the recent past to do exactly that as the easiest way to determine which version of the hardware I am running on.

Ignore the warnings unless something is malfunctioning. To most people, most of the time, they are meaningless and useless. The exist for those specific times when they are neither...and you will know the warning is relevant if you have some malfunction and that warning gives you a clue.

[Spinnifex]

Hello jiml8

Thank you for your answer. For a serious answer.
I must apologize a misunderstanding.
The warning appear not only in dmesg but also on startup.
Directly after I press Enter and before boot splash screen appear this message appear.
Beside the message that

Code: Select all

kvm

is disabled by bios.
This is okay. But the message about this tis is new to me.

So to check this I take a look into dmesg.
I am aware of your description of what kernel does and that you will have warnings on almost any system start.

What I am not aware of is this

Code: Select all

tis

message which is new to me.
If I had change my bios maybe that was the reason but I didn't.

Anyway as you explained there is no system error or malfunction.

I just want to understand a little bit more.

Thank you very much. Sorry for bad english since this is not my native language.

Spinnifex

[Spinnifex]

Hello

After last kernel update this message did not occur again.

Regards

[isadora]

Would you please mark this topic [SOLVED]?
You can do so by editing the title/subject of the first message in the topic.
Place [SOLVED] in front of subject/title.

Thanks ahead.