System log: "family specific matching fails" is that normal?

micho.mad

Registered
Hello,
Sorry for posting this in software and hardware, but I really don't know which area is concerned.
My MacBook Pro is a week old. Today I had to force quit FinalCutPro. I then decided to check the system log, just in case. Here's what looks strange to me (I removed all the other lines):

Code:
Apr 24 12:37:54 localhost kernel[0]: MCHC: family specific matching fails
Apr 24 12:37:54 localhost kernel[0]: MCH2: family specific matching fails
Apr 24 12:37:54 localhost kernel[0]: LPCB: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: IMAP: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: SBUS: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: TRIM: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: NVPM: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: OHC1: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: EHC1: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: OHC2: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: EHC2: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: GIGE: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: SATA: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: RP01: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: IXVE: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: P4MI: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: RP04: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: RP05: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: RP06: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: pci-bridge: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: GFX0: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: IGPU: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: ARPT: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: FRWR: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: HDEF: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: GFX0: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: IGPU: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: GFX0: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: IGPU: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: MCHC: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: IMAP: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: NVPM: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: LPCB: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: MCH2: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: HDEF: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: P4MI: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: SBUS: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: TRIM: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: GFX0: family specific matching fails
Apr 24 12:37:55 localhost kernel[0]: IGPU: family specific matching fails
Apr 24 12:37:56 localhost kernel[0]: GFX0: family specific matching fails
Apr 24 12:37:56 localhost kernel[0]: IGPU: family specific matching fails
Apr 24 12:37:56 localhost kernel[0]: IGPU: family specific matching fails
Apr 24 12:37:56 localhost kernel[0]: GFX0: family specific matching fails

However, the computer seems to work fine now. I was just wondering if this is normal.

Michel
 
Back
Top