[Gigabyte EP45-UD3L] CPU frequency reported incorrectly after overclocking
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
The stock speed of Intel E3300 is 2.5 GHz (200*12.5). I had pushed the FSB from 200 MHz to 300 MHz in the BIOS, giving 3.75 GHz (300*12.5). However, "cat /proc/cpuinfo" and "cpufreq-info" incorrectly shows 3.33, 2.67, 2.13, 1.6 GHz, which are probably based on 266 MHz FSB (266*12.5=3.33, 266*10=2.67, 266*8=2.13, 266*6=1.6).
"dmidecode --type processor" shows it at 3.75 GHz all the time, no matter which frequency or governor was selected in CPU Frequency Scaling Monitor.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-
ProcVersionSign
Uname: Linux 3.8.0-35-generic x86_64
NonfreeKernelMo
ApportVersion: 2.9.2-0ubuntu8.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
/dev/snd/
/dev/snd/
Date: Tue Dec 17 11:16:02 2013
InstallationDate: Installed on 2012-02-02 (684 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
MachineType: Gigabyte Technology Co., Ltd. EP45-UD3L
MarkForUpload: True
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.106
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-04-07 (254 days ago)
dmi.bios.date: 01/27/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F9
dmi.board.name: EP45-UD3L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: EP45-UD3L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
John Kuang, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http:// cdimage. ubuntu. com/daily- live/current/ . If the issue remains, could you please just make a comment to this.
Also, could you please test the latest upstream kernel available (not the daily folder, but the one at the top) following https:/ /wiki.ubuntu. com/KernelMainl ineBuilds ? It will allow additional upstream developers to examine the issue.Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: fixed-upstream fixed-upstream- VERSION- NUMBER
kernel-
kernel-
where VERSION-NUMBER is the version number of the kernel you tested. For example: fixed-upstream- v3.13-rc4
kernel-
This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: testing
needs-upstream-
If the mainline kernel does not fix this bug, please add the following tags: bug-exists- upstream bug-exists- upstream- VERSION- NUMBER
kernel-
kernel-
As well, please remove the tag: testing
needs-upstream-
Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.