|
Z3775 (meegopad) scheduler mishaps
As soon as I boot to my t01 meegopad (a z3775 intel baytrail atom pc stick) with Liquorix, I have two cores stuck maxed out at the burst frequency of 1.83~ghz and two others idling at 300-700mhz (according to cpufreq-info). htop is reporting no process as throttling. In fact, the machine seems quite idle being well under 5% usage of any core at any given time.
Letting the stick idle about for a couple of hours causes all 4 cores to max out at 1.83ghz and the ui become unresponsive (mouse and keyboard input in i3wm or switching to console with ctrl+alt+f1 isn't possible). This requires either SSHing into the machine to imitate a reboot or a hard (disconnect power or hold power button) reboot. For reference, the stock debian 3.16 kernel works fine but it lacks access to the sdcard access (it's too old AND there's the missing compile flag (CONFIG_PINCTRL_BAYTRAIL=y) in the all debian kernels as reported in bug #797949) and the wifi driver isn't targeting it since it's too old meaning you can't even compile a module for it. I've also heard people had luck with ubuntu... Anyhow, I'm fairly sure this is a scheduler problem (cpufreq-info identifies the governor as in power saving) but that's about all I can tell or do about it. I suspect the problem is impossible to debug without actually owning an atom device so I'm just putting this little report out there in hopes someone with a clue might find it useful. Peace out :) Back to top |
|||||
|
More for my own curiosity, can you install inxi and post:
inxi -v7 I'm curious to see this type of hardware. Make sure you have version 2.2.28, or 2.2.29, the latest, of inxi. And if you're feeling extra nice, run: inxi -xx@14 which will create then upload a system data debugger file to ftp. I'm more interested in just seeing what a device like this is actually made out of and what the linux tools see re its hardware configuration. I can pass this file along to damentz too in case it contains anything relevant to your issue. thanks. Back to top |
|||||
|
Actually, what happens if you disable intel pstate through a kernel parameter? Specifically, add this to your grub boot kernel parameters: intel_pstate=disable
I suspect that pstate is not ready for your cpu and you're probably better off with the old ondemand governor. Back to top |
|||||
|
Ok, lets start with the raw results:
3.16 debian stable kernel: :: Code :: "uname -r":
3.16.0-4-amd64 "inxi -v7": System: Host: HAL Kernel: 3.16.0-4-amd64 x86_64 (64 bit gcc: 4.8.4) Console: tty 0 dm: gdm3 Distro: Debian GNU/Linux 8 Machine: Mobo: AMI model: Aptio CRB Bios: American Megatrends v: T010001 date: 01/19/2015 CPU: Quad core Intel Atom Z3735F (-MCP-) cache: 1024 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10649 clock speeds: min/max: 499/1832 MHz 1: 1820 MHz 2: 1696 MHz 3: 1831 MHz 4: 1796 MHz Memory: Array-1 capacity: 4 GB devices: 1 EC: Multi-bit ECC Device-1: A1_DIMM0 size: 2 GB speed: 1333 MHz type: DDR3 bus width: 64 bits manufacturer: N/A part: N/A serial: N/A Graphics: Card: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display bus-ID: 00:02.0 chip-ID: 8086:0f31 Display Server: X.org 1.16.4 drivers: intel (unloaded: fbdev,vesa) tty size: 100x50 Advanced Data: N/A for root out of X Audio: Card Failed to Detect Sound Card! Sound: ALSA v: k3.16.0-4-amd64 Network: Card: Failed to Detect Network Card! WAN IP: ***.***.***.*** IF: eth0 ip: ***.***.***.*** ip-v6: ****::****:****:****:*** IF: wlan0 ip: N/A ip-v6: N/A Drives: Optical: No optical drives detected. Partition: ID-1: / size: 9.8G used: 6.8G (74%) fs: ext4 dev: /dev/mmcblk0p4 label: N/A uuid: ********-***-****-****-************ ID-2: /boot/efi size: 96M used: 43M (45%) fs: vfat dev: /dev/mmcblk0p1 label: SYSTEM uuid: ****-**** ID-3: /mnt/nfs/***/sdb1 size: 917G used: 709G (82%) fs: nfs4 remote: ***.***.***.***:/mnt/sdb1 ID-4: /mnt/nfs/***/sdc1 size: 459G used: 404G (93%) fs: nfs4 remote: ***.***.***.***:/mnt/sdc1 RAID: No RAID data: /proc/mdstat missing-is md_mod kernel module loaded? Unmounted: ID-1: /dev/mmcblk0 size: 31.27G label: N/A uuid: N/A ID-2: /dev/mmcblk0p2 size: 0.13G label: N/A uuid: N/A ID-3: /dev/mmcblk0p3 size: 15.05G fs: NTFS label: Windows uuid: **************** ID-4: /dev/mmcblk0p5 size: 5.24G fs: NTFS label: Images uuid: **************** ID-5: /dev/mmcblk0boot1 size: 0.00G label: N/A uuid: N/A ID-6: /dev/mmcblk0boot0 size: 0.00G label: N/A uuid: N/A Sensors: System Temperatures: cpu: 47.0C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 126 Uptime: 3 min Memory: 121.5/1953.6MB Init: systemd v: 215 runlevel: 5 Gcc sys: 4.9.2 alt: 4.8 Client: Shell (bash 4.3.301 running in tty 0) inxi: 2.2.28 "cpufreq-info": cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 0.97 ms. hardware limits: 500 MHz - 1.83 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 500 MHz and 1.83 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.35 GHz (asserted by call to hardware). analyzing CPU 1: driver: intel_pstate CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 0.97 ms. hardware limits: 500 MHz - 1.83 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 500 MHz and 1.83 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.34 GHz (asserted by call to hardware). analyzing CPU 2: driver: intel_pstate CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 0.97 ms. hardware limits: 500 MHz - 1.83 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 500 MHz and 1.83 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.33 GHz (asserted by call to hardware). analyzing CPU 3: driver: intel_pstate CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 0.97 ms. hardware limits: 500 MHz - 1.83 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 500 MHz and 1.83 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.33 GHz (asserted by call to hardware). 4.2 liquorix kernel: :: Code :: "uname -r":
4.2-5.dmz.1-liquorix-amd64 "inxi -v7": System: Host: HAL Kernel: 4.2-5.dmz.1-liquorix-amd64 x86_64 (64 bit gcc: 4.9.3) Console: tty 0 dm: gdm3 Distro: Debian GNU/Linux 8 Machine: Mobo: AMI model: Aptio CRB Bios: American Megatrends v: T010001 date: 01/19/2015 CPU: Quad core Intel Atom Z3735F (-MCP-) cache: 1024 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10649 clock speeds: min/max: 499/1832 MHz 1: 1836 MHz 2: 1833 MHz 3: 974 MHz 4: 642 MHz Memory: Array-1 capacity: 4 GB devices: 1 EC: Multi-bit ECC Device-1: A1_DIMM0 size: 2 GB speed: 1333 MHz type: DDR3 bus width: 64 bits manufacturer: N/A part: N/A serial: N/A Graphics: Card: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display bus-ID: 00:02.0 chip-ID: 8086:0f31 Display Server: X.org 1.16.4 drivers: intel (unloaded: fbdev,vesa) tty size: 122x49 Advanced Data: N/A for root out of X Audio: Card Failed to Detect Sound Card! Sound: ALSA v: k4.2-5.dmz.1-liquorix-amd64 Network: Card: Failed to Detect Network Card! WAN IP: ***.***.***.*** IF: eth0 ip: ***.***.***.*** ip-v6: ****::****:****:****:*** Drives: Optical: No optical drives detected. Partition: ID-1: / size: 9.8G used: 6.8G (74%) fs: ext4 dev: /dev/mmcblk0p4 label: N/A uuid: ********-***-****-****-************ ID-2: /boot/efi size: 96M used: 43M (45%) fs: vfat dev: /dev/mmcblk0p1 label: SYSTEM uuid: ****-**** ID-3: /mnt/nfs/***/sdb1 size: 917G used: 709G (82%) fs: nfs4 remote: ***.***.***.***:/mnt/sdb1 ID-4: /mnt/nfs/***/sdc1 size: 459G used: 404G (93%) fs: nfs4 remote: ***.***.***.***:/mnt/sdc1 RAID: No RAID data: /proc/mdstat missing-is md_mod kernel module loaded? Unmounted: ID-1: /dev/mmcblk0 size: 31.27G label: N/A uuid: N/A ID-2: /dev/mmcblk0p2 size: 0.13G label: N/A uuid: N/A ID-3: /dev/mmcblk0p3 size: 15.05G fs: NTFS label: Windows uuid: **************** ID-4: /dev/mmcblk0p5 size: 5.24G fs: NTFS label: Images uuid: **************** ID-5: /dev/mmcblk0boot1 size: 0.00G label: N/A uuid: N/A ID-6: /dev/mmcblk0boot0 size: 0.00G label: N/A uuid: N/A Sensors: System Temperatures: cpu: 44.0C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 141 Uptime: 1 min Memory: 119.2/1948.8MB Init: systemd v: 215 runlevel: 5 Gcc sys: 4.9.2 alt: 4.8 Client: Shell (bash 4.3.301 running in tty 0) inxi: 2.2.28 "cpufreq-info": cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 0.97 ms. hardware limits: 500 MHz - 1.83 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 500 MHz and 1.83 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.84 GHz. analyzing CPU 1: driver: intel_pstate CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 0.97 ms. hardware limits: 500 MHz - 1.83 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 500 MHz and 1.83 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.83 GHz. analyzing CPU 2: driver: intel_pstate CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 0.97 ms. hardware limits: 500 MHz - 1.83 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 500 MHz and 1.83 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 769 MHz. analyzing CPU 3: driver: intel_pstate CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 0.97 ms. hardware limits: 500 MHz - 1.83 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 500 MHz and 1.83 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 861 MHz. 4.3 liquorix kernel: :: Code :: "uname -r":
4.3-0.dmz.1-liquorix-amd64 "inxi -v7": System: Host: HAL Kernel: 4.3-0.dmz.1-liquorix-amd64 x86_64 (64 bit gcc: 5.2.1) Console: tty 0 dm: gdm3 Distro: Debian GNU/Linux 8 Machine: Mobo: AMI model: Aptio CRB Bios: American Megatrends v: T010001 date: 01/19/2015 CPU: Quad core Intel Atom Z3735F (-MCP-) cache: 1024 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10649 clock speeds: min/max: 499/1832 MHz 1: 709 MHz 2: 686 MHz 3: 566 MHz 4: 620 MHz Memory: Array-1 capacity: 4 GB devices: 1 EC: Multi-bit ECC Device-1: A1_DIMM0 size: 2 GB speed: 1333 MHz type: DDR3 bus width: 64 bits manufacturer: N/A part: N/A serial: N/A Graphics: Card: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display bus-ID: 00:02.0 chip-ID: 8086:0f31 Display Server: X.org 1.16.4 drivers: intel (unloaded: fbdev,vesa) tty size: 100x50 Advanced Data: N/A for root out of X Audio: Card Failed to Detect Sound Card! Sound: ALSA v: k4.3-0.dmz.1-liquorix-amd64 Network: Card: Failed to Detect Network Card! WAN IP: ***.***.***.*** IF: eth0 ip: ***.***.***.*** ip-v6: ****::****:****:****:*** Drives: Optical: No optical drives detected. Partition: ID-1: / size: 9.8G used: 6.8G (74%) fs: ext4 dev: /dev/mmcblk0p4 label: N/A uuid: ********-***-****-****-************ ID-2: /boot/efi size: 96M used: 43M (45%) fs: vfat dev: /dev/mmcblk0p1 label: SYSTEM uuid: ****-**** ID-3: /mnt/nfs/***/sdb1 size: 917G used: 709G (82%) fs: nfs4 remote: ***.***.***.***:/mnt/sdb1 ID-4: /mnt/nfs/***/sdc1 size: 459G used: 404G (93%) fs: nfs4 remote: ***.***.***.***:/mnt/sdc1 RAID: No RAID data: /proc/mdstat missing-is md_mod kernel module loaded? Unmounted: ID-1: /dev/mmcblk0 size: 31.27G label: N/A uuid: N/A ID-2: /dev/mmcblk0p2 size: 0.13G label: N/A uuid: N/A ID-3: /dev/mmcblk0p3 size: 15.05G fs: NTFS label: Windows uuid: **************** ID-4: /dev/mmcblk0p5 size: 5.24G fs: NTFS label: Images uuid: **************** ID-5: /dev/mmcblk0boot1 size: 0.00G label: N/A uuid: N/A ID-6: /dev/mmcblk0boot0 size: 0.00G label: N/A uuid: N/A Sensors: System Temperatures: cpu: 45.0C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 134 Uptime: 2 min Memory: 118.9/1948.8MB Init: systemd v: 215 runlevel: 5 Gcc sys: 4.9.2 alt: 4.8 Client: Shell (bash 4.3.301 running in tty 0) inxi: 2.2.28 "cpufreq-info": cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 0.97 ms. hardware limits: 500 MHz - 1.83 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 500 MHz and 1.83 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.04 GHz (asserted by call to hardware). analyzing CPU 1: driver: intel_pstate CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 0.97 ms. hardware limits: 500 MHz - 1.83 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 500 MHz and 1.83 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.21 GHz (asserted by call to hardware). analyzing CPU 2: driver: intel_pstate CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 0.97 ms. hardware limits: 500 MHz - 1.83 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 500 MHz and 1.83 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 830 MHz (asserted by call to hardware). analyzing CPU 3: driver: intel_pstate CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 0.97 ms. hardware limits: 500 MHz - 1.83 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 500 MHz and 1.83 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 572 MHz (asserted by call to hardware). "cpufreq-info" after running firefox(iceweasel) for a bit, closing it and verifying the process is dead, and then idling for 10-15 minutes: cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 0.97 ms. hardware limits: 500 MHz - 1.83 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 500 MHz and 1.83 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.84 GHz. analyzing CPU 1: driver: intel_pstate CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 0.97 ms. hardware limits: 500 MHz - 1.83 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 500 MHz and 1.83 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.83 GHz. analyzing CPU 2: driver: intel_pstate CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 0.97 ms. hardware limits: 500 MHz - 1.83 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 500 MHz and 1.83 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.01 GHz. analyzing CPU 3: driver: intel_pstate CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 0.97 ms. hardware limits: 500 MHz - 1.83 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 500 MHz and 1.83 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 964 MHz. "cpufreq-info" after setting GRUB_CMDLINE_LINUX_DEFAULT="intel_pstate=disable" in /etc/default/grub, running "update-grub", rebooting and while running iceweasel: cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 498 MHz - 1.33 GHz available frequency steps: 1.33 GHz, 1.33 GHz, 1.25 GHz, 1.16 GHz, 1.08 GHz, 996 MHz, 913 MHz, 830 MHz, 747 MHz, 664 MHz, 581 MHz, 498 MHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance current policy: frequency should be within 498 MHz and 1.33 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 498 MHz (asserted by call to hardware). cpufreq stats: 1.33 GHz:5.39%, 1.33 GHz:0.00%, 1.25 GHz:0.00%, 1.16 GHz:0.27%, 1.08 GHz:0.51%, 996 MHz:1.09%, 913 MHz:1.00%, 830 MHz:1.04%, 747 MHz:1.60%, 664 MHz:3.00%, 581 MHz:6.32%, 498 MHz:79.77% (589) analyzing CPU 1: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 10.0 us. hardware limits: 498 MHz - 1.33 GHz available frequency steps: 1.33 GHz, 1.33 GHz, 1.25 GHz, 1.16 GHz, 1.08 GHz, 996 MHz, 913 MHz, 830 MHz, 747 MHz, 664 MHz, 581 MHz, 498 MHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance current policy: frequency should be within 498 MHz and 1.33 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 498 MHz (asserted by call to hardware). cpufreq stats: 1.33 GHz:8.37%, 1.33 GHz:0.00%, 1.25 GHz:0.00%, 1.16 GHz:0.48%, 1.08 GHz:0.50%, 996 MHz:0.89%, 913 MHz:0.82%, 830 MHz:1.41%, 747 MHz:1.74%, 664 MHz:2.21%, 581 MHz:3.80%, 498 MHz:79.78% (482) analyzing CPU 2: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 10.0 us. hardware limits: 498 MHz - 1.33 GHz available frequency steps: 1.33 GHz, 1.33 GHz, 1.25 GHz, 1.16 GHz, 1.08 GHz, 996 MHz, 913 MHz, 830 MHz, 747 MHz, 664 MHz, 581 MHz, 498 MHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance current policy: frequency should be within 498 MHz and 1.33 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 664 MHz (asserted by call to hardware). cpufreq stats: 1.33 GHz:5.45%, 1.33 GHz:0.00%, 1.25 GHz:0.00%, 1.16 GHz:0.33%, 1.08 GHz:0.36%, 996 MHz:0.64%, 913 MHz:0.82%, 830 MHz:1.53%, 747 MHz:2.56%, 664 MHz:4.28%, 581 MHz:7.82%, 498 MHz:76.22% (728) analyzing CPU 3: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 10.0 us. hardware limits: 498 MHz - 1.33 GHz available frequency steps: 1.33 GHz, 1.33 GHz, 1.25 GHz, 1.16 GHz, 1.08 GHz, 996 MHz, 913 MHz, 830 MHz, 747 MHz, 664 MHz, 581 MHz, 498 MHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance current policy: frequency should be within 498 MHz and 1.33 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 498 MHz (asserted by call to hardware). cpufreq stats: 1.33 GHz:5.54%, 1.33 GHz:0.00%, 1.25 GHz:0.00%, 1.16 GHz:0.33%, 1.08 GHz:0.61%, 996 MHz:0.48%, 913 MHz:1.07%, 830 MHz:1.54%, 747 MHz:2.19%, 664 MHz:3.86%, 581 MHz:6.70%, 498 MHz:77.66% (658) Notes: inxi 2.2.28-1 (from repositories). 4.3 works fine at first glance. Then fails. 4.3 with "intel_pstate=disable" kills off the stepping altogether and sets the cores at the lowest 498 MHz. Review: The pstate driver seems to have regressed since 3.16 but there's no real "control group" aside from the older kernel running an older pstate driver. A proper test would be to test the older driver in a new kernel but that's beyond my pay-grade ;) Back to top |
|||||
|
RamiK,
With pstate disabled, cpufreq should fall back to the ondemand governor. I suspect that if you incur high cpu usage, your core frequency will increase. Also, as indicated in your raw output, when you disable intel_pstate, it fell back to acpi-cpufreq and it properly detected all possible frequencies, except for turbo (which is OK, acpi-cpufreq does not know about that). Also, just because your CPU frequency is set to maximum doesn't mean it's misconfigured. The best indication that it's working is that the heat output from your laptop or desktop is reduced when idle and your system runs faster under load. If your heat output is higher than with ondemand, then you definitely found a bug. If it's about the same or immeasurable, that's just the intel_pstate governor deciding that it's best that your cores idle at maximum speed. Back to top |
|||||
|
:: Quote :: With pstate disabled, cpufreq should fall back to the ondemand governorWell, I tried it out with just firefox/iceweasel which is usually enough to push all 4 cores all the way to 1.33-1.84Ghz. Specifically, as I'm writing now using the 3.16 kernel, I'm seeing 1.33Ghz. But, when I just scroll the window up and down a couple of time and then run cpufreq-info I reliably get 1.84Ghz on all cores. With the pstate disabled and running 4.3 I can't do nothing to push it above the first step. It's stuck at 498mhz regardless and the responsiveness is very sluggish: Even SSHing into the box felt noticeable which is about 200-300ms latency worth I'm guessing. :: Quote :: properly detected all possible frequencies, except for turboI don't think turbo works anyhow unless I mod the device with a physical fan (http://forum.x86pad.com/t/meegopad-t02-modding-performance/206/3). :: Quote :: just because your CPU frequency is set to maximum doesn't mean it's misconfiguredWell, I was getting all 4 cores peaking at 1.83Ghz 15minutes after closing firefox AND by SSHing into the machine without it running anything aside from the logged-in xserver' instance that was running i3wm... There's no torrent servers and I'm only mounting NFS so it should really be idling all 4 cores not peaking them... No? Back to top |
|||||
|
RamiK, thanks a lot for taking the time to show the inxi data, I'm glad to see how much of inxi works on this platform, I'm sorry I neglected to mention the -z option, which filters out ip and other sensitive information from the output (inxi -v7 -z).
As I expected, one thing, actually two, here, doesn't work: /dev/mmcblk0p4 fails to register both on the partition and on the disk data section. I'll look into that and correct it. Back to top |
|||||
|
RamiK, can you test a possible fix? Do:
wget -O /usr/bin/inxi smxi.org/inxi as root to force the update to current, 2.2.30 Then show: inxi -IDpluodxxxz Which will show me if the fix worked. Also, show: cat /proc/partitions OR use: inxi -xx@14 so I can see how the system reports mmcblock data. Back to top |
|||||
|
Not sure what's the problem exactly but here you go (using 4.3):
:: Code :: cat /proc/partitions
major minor #blocks name 179 0 30535680 mmcblk0 179 1 102400 mmcblk0p1 179 2 131072 mmcblk0p2 179 3 14694400 mmcblk0p3 179 4 10484736 mmcblk0p4 179 5 5120000 mmcblk0p5 179 24 4096 mmcblk0rpmb 179 16 4096 mmcblk0boot1 179 8 4096 mmcblk0boot0 inxi -IDpluodxxxz :: Code :: Drives: Optical: No optical drives detected.
Partition: ID-1: / size: 9.8G used: 6.8G (74%) fs: ext4 dev: /dev/mmcblk0p4 label: N/A uuid: ********-****-****-****-************ ID-2: /boot/efi size: 96M used: 43M (45%) fs: vfat dev: /dev/mmcblk0p1 label: SYSTEM uuid: ****-**** ID-3: /mnt/***/sdc1 size: 459G used: 370G (86%) fs: nfs4 remote: 10.0.0.10:/mnt/sdc1 ID-4: /mnt/***/sdb1 size: 917G used: 709G (82%) fs: nfs4 remote: 10.0.0.10:/mnt/sdb1 Unmounted: ID-1: /dev/mmcblk0 size: 31.27G label: N/A uuid: N/A ID-2: /dev/mmcblk0p2 size: 0.13G label: N/A uuid: N/A ID-3: /dev/mmcblk0p3 size: 15.05G fs: NTFS label: Windows uuid: **************** ID-4: /dev/mmcblk0p5 size: 5.24G fs: NTFS label: Images uuid: **************** ID-5: /dev/mmcblk0boot1 size: 0.00G label: N/A uuid: N/A ID-6: /dev/mmcblk0boot0 size: 0.00G label: N/A uuid: N/A Info: Processes: 147 Uptime: 2 min Memory: 368.2/1948.8MB Init: systemd v: 215 runlevel: 5 Gcc sys: 4.9.2 alt: 4.8 Client: Shell (bash 4.3.301 running in x-terminal-emul) inxi: 2.2.30 [/code] Back to top |
|||||
|
The problem was no system data, and not seeing clearly.
I had mmcblock instead of mmcblk so the -D hard drive correctly saw no mmcblock devices, heh. 2.2.31 should have that corrected, give it a try. Thanks for the data. Back to top |
|||||
|
All times are GMT - 8 Hours
|
|||||