>-----Original Message-----
>From: S.Çaglar Onur [mailto:[email protected]]
>Sent: Friday, October 13, 2006 11:34 AM
>To: Pallipadi, Venkatesh
>Cc: Dave Jones; [email protected]
>Subject: Re: Ondemand/Conservative not working with 2.6.18
>
>11 Eki 2006 Çar 22:00 tarihinde, Pallipadi, Venkatesh şunları
>yazmıştı:
>> I guess I misunderstood the original issue. You have
>available_frequencies
>> showing all the values and after you load ondemand,
>frequency remains at
>> the highest, even though CPUs are idle. Is this correct?
>>
>> And everything above used to work fine with 2.6.16?
>>
>> Can you configure with CPU_FREQ_DEBUG and do "echo 5 >
>> /sys/module/cpufreq/parameter/debug" before switching the governor to
>> ondemand and see whether you see any messages in dmesg?
>
>I just found a workaround of my problem, if system boots with
>ac adapter
>plugged then ondemand or conservative governors are not working, but
>unplugging the adapter and waiting some seconds, plug it back
>solves this
>issue and ondemand/conservative governors are starts to run as
>expected.
>
>What should i do now? If im not wrong it seems like acpi
>subsystem problem
>(and just to be sure, i disassembled my dsdt, iacl claims its
>error/warning
>free)
>
Sorry for the delayed response. This is still very mysterious to me..
Do you see anything interesting in dmesg after you try this ac adapter unplug and plug back routine? Can you send me the dmesg. Better still open a bugzilla at bugme.osdl.org and stick the dmesg and acpidump there.
One possible reason for this is, somehow idle statistics is getting all wrong and ondemand thinks CPU is busy, even though it is idle. I have seen this happening earlier when there are issues with local APIC interrupts in deep C-states on dual core systems. But, here it is a single core CPU. Right? Can you also get the output of
#cat /proc/interrupts; sleep 10; cat /proc/interrupts
On your system when ondemand is not working and when it is working (After your unplug-plug workaround.
Thanks,
Venki
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
