On Wednesday, November 28, 2012 12:44:54 AM Rafael J. Wysocki wrote: > On Tuesday, November 27, 2012 11:38:01 PM Rafał Bilski wrote: > > > > > On Tuesday, November 27, 2012 10:13:55 PM Rafal Bilski wrote: > > >> This is only solution I can think of. User decides if he wants this > > >> driver on his machine. I don't have enough knowledge and time to find > > >> the reason why same code works on some machines and doesn't on others > > >> which use same, or very similar, chipset and processor. > > > I always have problems with patches like this one, because they are pretty much > > > guaranteed to make someone complain. > > > > > > Is there any way to blacklist the affected machine you have? > > > > > > Rafael > > No. Also problem seems to be larger than one machine. Also weirder. > > One user claims his processor can't run below some frequency even > > if it should be perfectly capable of doing so. System in question > > freezes straight away. In past on good system I could change > > frequency at least a couple of times without any protection. Just by > > a chance. I tried to investigate "weird CPU 0 not listed by the BIOS" > > message, but I have nothing. Also I seem to have far less time for > > anything than in the past. > > OK, I'll take the patch, then, but I won't include it in my first v3.8 pull > request. I'm queuing it up for submission as v3.8 material later in the cycle. Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
