Comment 1 by mohamed khairy, Apr 29, 2012
merged to ermac branch when using DropSSDT=Yes cause panic
Comment 2 by Cosmosis Jones, May 4, 2012
where did it panic? what cpu wher eu using when it panicd? you have a debug log. i have an idea just was wdonering where it panicd on you
Comment 6 by mohamed khairy, May 7, 2012
currently don't use trunk as it doesnt support Mlion so using ErmaC branch ready compiled
Sign in to reply to this comment.
Reported by Moik The, Apr 25, 2012
Howdi! Since I got my new Sandy Bridge Core i7 2600 the automatic generation of C and P states never worked for me. First I noticed my DSDT missed the ProcessorOPs which I added as followed: Scope (_PR) { Processor (CPU0, 0x00, 0x00000410, 0x06) {} Processor (CPU1, 0x01, 0x00000410, 0x06) {} Processor (CPU2, 0x02, 0x00000410, 0x06) {} Processor (CPU3, 0x03, 0x00000410, 0x06) {} Processor (CPU4, 0x04, 0x00000410, 0x06) {} Processor (CPU5, 0x05, 0x00000410, 0x06) {} Processor (CPU6, 0x06, 0x00000410, 0x06) {} Processor (CPU7, 0x07, 0x00000410, 0x06) {} } Pretty standard I guess. Then the state generation reported me "insane control values" as my maximum multiplier has been detected as value 0x00. After looking at the code I noticed that the max state has been read from the wrong location. Here's a patch fixing it. Please not that I also added some more debugging output which may be removed again. Greetz, Mike