Closed RR7 closed 9 years ago
okay, i may have jumped the gun on this, i did a kextunload/kextload on it and it logged okay, i guess its just writing to the log before the log starts or something!
I haven't done that, but I will give it a try (later today) and see what it does here.
Maybe it works when you add the msgbuf=
I am using msgbuf=393216 (384 MB).
No problem here with: msgbuf=393216
cool, thanks. it was also fine when i reloaded the kext, so i think it was more to do with perhaps it logging too early, MAYBE because i booted from an SSD, i'm not sure. but it seems good. i did notice on the output there ws a couple of lines saying if (devid==.... almost like it was logging the query rather than the result. i didn't see this on the linux output.
Correct. You will see some debug info, like what generation it is, to help me fix errors. Will be removed in the next update.
on the computer i'm interested in diagnosing, i seem to be missing the start of the output, it starts here in the system.log:
23/08/2014 18:46:34.000 kernel[0]: FDI_RXA_IMR................: 0x000008ff 23/08/2014 18:46:34.000 kernel[0]: FDI_RXB_IIR................: 0x00000000 23/08/2014 18:46:34.000 kernel[0]: FDI_RXB_IMR................: 0x000008ff 23/08/2014 18:46:34.000 kernel[0]: PCH_ADPA...................: 0x00c40000 (disabled, transcoder A, -hsync, -vsync) 23/08/2014 18:46:34.000 kernel[0]: HDMIB......................: 0x00000018 (disabled pipe A 8bpc SDVO DVI audio disabled +vsync +hsync non-detected) 23/08/2014 18:46:34.000 kernel[0]: HDMIC......................: 0x00000018 (disabled pipe A 8bpc SDVO DVI audio disabled +vsync +hsync non-detected) 23/08/2014 18:46:34.000 kernel[0]: HDMID......................: 0x0000001c (disabled pipe A 8bpc SDVO DVI audio disabled +vsync +hsync detected) 23/08/2014 18:46:34.000 kernel[0]: PCH_LVDS...................: 0x00000000 (disabled, pipe A, 18 bit, 1 channel)
..etc
however i can see all the MSR register info scroll past, so its like it runs out of buffer space or something.
i tested on my other computer that is also IVB but no IGPU and it logs a similar amount of data, but since there is no IGPU i can see all the MSR stuff:
23/08/2014 18:17:35.000 kernel[0]: AICPUPMI: v1.0 Copyright © 2012-2014 Pike R. Alpha. All rights reserved 23/08/2014 18:17:35.000 kernel[0]: AICPUPMI: logMSRs............................: 1 23/08/2014 18:17:35.000 kernel[0]: AICPUPMI: logIGPU............................: 0 23/08/2014 18:17:35.000 kernel[0]: AICPUPMI: logIntelRegs.......................: 1 23/08/2014 18:17:35.000 kernel[0]: AICPUPMI: logCStates.........................: 1 23/08/2014 18:17:35.000 kernel[0]: AICPUPMI: logIPGStyle........................: 1 23/08/2014 18:17:35.000 kernel[0]: AICPUPMI: InitialTSC.........................: 0x1514d624ea 23/08/2014 18:17:35.000 kernel[0]: AICPUPMI: MWAIT C-States.....................: 4384 23/08/2014 18:17:35.000 kernel[0]: AICPUPMI: MSR_CORE_THREAD_COUNT......(0x35) : 0x40008
..etc
the power state logs all come out fine so i guess its just in the new register dump code.