Please specify the relevant kernel package in the RPM field.

As a general request, identifiying the relevant RPM greatly helps in triaging and thus will help bugs be triaged faster, since we have limited resource for those tasks. You're welcome to join the bug squad team, that said, given how used you are to using bugzilla :).

Ok, my bad, it's not from the kernel but from drakxtools apparently, since it creates the cpufreq file.

Source RPM: (none) => drakxtools
Keywords: NEEDINFO => (none)
CC: (none) => tmb
Assignee: bugsquad => thierry.vignaud

(In reply to Samuel VERSCHELDE from comment #1)
> Please specify the relevant kernel package in the RPM field.
> 
> As a general request, identifiying the relevant RPM greatly helps in
> triaging and thus will help bugs be triaged faster, since we have limited
> resource for those tasks.

As a general rule, I supply the offending rpm package when I can run down the full file name on the system.

> You're welcome to join the bug squad team,

Thank for your kind offer, but I have all the spinning plates in the air that I can manage at the moment. :)

Large amount of time being wasted just getting a reliable log out/in plasma session and/or getting my release 6 back to booting up under 50 seconds.
Up to yesterday it was taking +2 minutes.

> that said, given how used you are to using bugzilla :).

I have my custom Mageia url link pointing to any new/change bugs in the last 3 days to help make I don't open too many duplicates  :(
have pretty poor luck running down something I was pretty sure was in the database.

It might be a side effect of the harddrake service:
http://gitweb.mageia.org/software/drakx/tree/perl-install/cpufreq.pm#n100

We should maybe be stricter for matching powernow k8
Can you attach the content of your /proc/cpuinfo file?

Keywords: (none) => NEEDINFO
CC: (none) => mageia

Created attachment 7416 [details]
cat /proc/cpuinfo info

Workaround:
 remove powernow-k8 from /etc/modprobe.preload.d/cpufreq

Converted my setup to use systemd-networkd for 20 mil-second per nic improvement in boot time.

Closing this bug report.

Resolution: (none) => FIXED
Status: NEW => RESOLVED

Sorry, I was on the wrong bug. Problem still exists.

Resolution: FIXED => (none)
Status: RESOLVED => REOPENED

Hello,
Here info from a system with the same problem :
cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 16
model : 4
model name : AMD Phenom(tm) II X4 965 Processor
stepping : 3
microcode : 0x10000c8
cpu MHz : 2700.000
cache size : 512 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate vmmcall npt lbrv svm_lock nrip_save
bugs : tlb_mmatch apic_c1e fxsave_leak sysret_ss_attrs null_seg amd_e400 spectre_v1 spectre_v2
bogomips : 6845.80
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

CC: (none) => yves.brungard_mageia

I see the same problem after I run an upgrade from one version of Mageia to another.
For example from 6 to 7 or from 7 to 8.

I work around this by removing powernow-k8 from /etc/modprobe.preload.d/cpufreq 


Unfortunately if there is an upgrade of Mageia then /etc/modprobe.preload.d/cpufreq gets overwritten with the wrong info.


By the way the system has an AMD Athlon II X4 635 Processor
 
cat /proc/cpuinfo
processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 16
model		: 5
model name	: AMD Athlon(tm) II X4 635 Processor
stepping	: 2
microcode	: 0x10000db
cpu MHz		: 2900.000
cache size	: 512 KB
physical id	: 0
siblings	: 4
core id		: 0
cpu cores	: 4
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate vmmcall npt lbrv svm_lock nrip_save
bugs		: tlb_mmatch apic_c1e fxsave_leak sysret_ss_attrs null_seg amd_e400 spectre_v1 spectre_v2
bogomips	: 5826.51
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

CC: (none) => rihoward1

Note that acpi-cpufreq replaced powernow-k8 for modern AMD CPUs starting with kernel 3.7