1 |
Fernando Boaglio wrote: |
2 |
|
3 |
>Hmm... |
4 |
> |
5 |
>Please check my kernel config file: |
6 |
> |
7 |
> |
8 |
> |
9 |
>>cat /usr/src/linux/.config | grep -i cpu |
10 |
>> |
11 |
>> |
12 |
># CONFIG_GENERIC_CPU is not set |
13 |
>CONFIG_X86_CPUID=y |
14 |
>CONFIG_SPLIT_PTLOCK_CPUS=4 |
15 |
># CPU Frequency scaling |
16 |
>CONFIG_CPU_FREQ=y |
17 |
>CONFIG_CPU_FREQ_TABLE=y |
18 |
># CONFIG_CPU_FREQ_DEBUG is not set |
19 |
>CONFIG_CPU_FREQ_STAT=y |
20 |
># CONFIG_CPU_FREQ_STAT_DETAILS is not set |
21 |
>CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y |
22 |
># CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set |
23 |
>CONFIG_CPU_FREQ_GOV_PERFORMANCE=y |
24 |
>CONFIG_CPU_FREQ_GOV_POWERSAVE=y |
25 |
>CONFIG_CPU_FREQ_GOV_USERSPACE=y |
26 |
>CONFIG_CPU_FREQ_GOV_ONDEMAND=y |
27 |
>CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y |
28 |
># CPUFreq processor drivers |
29 |
># CONFIG_X86_ACPI_CPUFREQ is not set |
30 |
># CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set |
31 |
> |
32 |
>Should I change anything ? |
33 |
> |
34 |
>Maybe I should remove CONFIG_CPU_FREQ_GOV_CONSERVATIVE and |
35 |
>CONFIG_CPU_FREQ_GOV_POWERSAVE... |
36 |
> |
37 |
>=) |
38 |
> |
39 |
>On 4/27/06, Sergio Polini <sp_rm_it@×××××.it> wrote: |
40 |
> |
41 |
> |
42 |
>>Fernando Boaglio: |
43 |
>> |
44 |
>> |
45 |
>>>It's not about startup time, it's about running time, sometimes the |
46 |
>>>systems freezes |
47 |
>>>a little bit, just like asking for more CPU or RAM. |
48 |
>>> |
49 |
>>> |
50 |
>>I'ld look at the cpu frequency governor. |
51 |
>>From /usr/src/linux/drivers/cpufreq/Kconfig, about the 'conservative' |
52 |
>>governor: |
53 |
>> |
54 |
>>"If you have a desktop machine then you should really be considering |
55 |
>>the 'ondemand' governor instead, however if you are using a laptop, |
56 |
>>PDA or even an AMD64 based computer (due to the unacceptable |
57 |
>>step-by-step latency issues between the minimum and maximum frequency |
58 |
>>transitions in the CPU) you will probably want to use this governor." |
59 |
>> |
60 |
>>As far as I can understand, this means that AMD64 takes "a lot" of |
61 |
>>time to switch between two frequencies, so "the system freezes a |
62 |
>>little bit" when this happens. |
63 |
>> |
64 |
>>This is why I've choosen the conservative governor for my HP dv5000 |
65 |
>>laptop. |
66 |
>> |
67 |
>>My 2 cents ;-) |
68 |
>> |
69 |
>>Sergio |
70 |
>> |
71 |
>>-- |
72 |
>>gentoo-amd64@g.o mailing list |
73 |
>> |
74 |
>> |
75 |
>> |
76 |
>> |
77 |
> |
78 |
> |
79 |
>-- |
80 |
>[]'s |
81 |
>boaglio@×××××.com |
82 |
> |
83 |
> |
84 |
> |
85 |
Also, check your hard drive parameters and make sure DMA is on. I |
86 |
always get tripped up by this between an Intel 2.53 machine and my AMD64 |
87 |
3200+ machine. It seems that everytime I rebuild the kernel on the |
88 |
AMD64 I forget to set the correct values for DMA access. |
89 |
Chris |
90 |
-- |
91 |
gentoo-amd64@g.o mailing list |