Forum Debian Users Gang

darko · 2017-02-19 13:26:23

Witam.
Jako, że to jest mój pierwszy post na tym forum, to chciałem wszystkich pozdrowić, oraz poprosić o pomoc.
Mianowicie w moim laptopie występuje problem z wydajnością po powrocie ze stanu wstrzymania. Objawia się to tym, że po wybudzeniu ze stanu wstrzymania procesor nie pracuje z większą częstotliwością jak 600-700 MHz. Nie zależnie od obciążenia.
Co może powodować takie zachowanie?
System to Debian 8.6 Jessie ze standardowym jądrem.
Laptop to Dell e6520 z i3.

Marek607 · 2017-02-19 13:42:02

Sprawdź jak masz ustawione taktowanie CPU:

https://wiki.debian.org/HowTo/CpuFrequencyScaling

ilin · 2017-02-19 13:42:12

Ja bym na początek spróbował nowszego jądra z backportów.
Sam mam della 5420 z i3 i nic takiego nie występuje u mnie.

darko · 2017-02-19 13:51:11

Jeżeli chodzi o taktowanie to:

Kod:

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: 800 MHz - 3.20 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.20 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 633 MHz (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: 800 MHz - 3.20 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.20 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 632 MHz (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: 800 MHz - 3.20 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.20 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 614 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: 800 MHz - 3.20 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.20 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 610 MHz (asserted by call to hardware).

Ustawienie są raczej normalne, poza tym, że procek stoi na 600MHz.

Co do kernela backport to chyba z tego co pamiętam miałem problem ze sterownikami nvidi.

ilin · 2017-02-19 14:03:03

Wrzuć gdzieś na wkleja i podlinkuj zawartość /var/log/dmesg po wybudzeniu.

darko · 2017-02-19 14:24:43

http://www.wklej.org/id/3046208/ -dmesg
Zmieniłem narazie sterowanie z intel_pstate na acpi-cpufreq i zobaczę, czy to da jakiś efekt.

Jak narazie pomogło.

Ostatnio edytowany przez darko (2017-02-19 17:31:02)

Time (s)	Query
0.00012	SET CHARSET latin2
0.00004	SET NAMES latin2
0.00120	SELECT u., g., o.logged FROM punbb_users AS u INNER JOIN punbb_groups AS g ON u.group_id=g.g_id LEFT JOIN punbb_online AS o ON o.ident='52.15.72.229' WHERE u.id=1
0.00064	REPLACE INTO punbb_online (user_id, ident, logged) VALUES(1, '52.15.72.229', 1732221919)
0.00046	SELECT * FROM punbb_online WHERE logged<1732221619
0.00063	SELECT t.subject, t.closed, t.num_replies, t.sticky, f.id AS forum_id, f.forum_name, f.moderators, fp.post_replies, 0 FROM punbb_topics AS t INNER JOIN punbb_forums AS f ON f.id=t.forum_id LEFT JOIN punbb_forum_perms AS fp ON (fp.forum_id=f.id AND fp.group_id=3) WHERE (fp.read_forum IS NULL OR fp.read_forum=1) AND t.id=29370 AND t.moved_to IS NULL
0.00008	SELECT search_for, replace_with FROM punbb_censoring
0.00141	SELECT u.email, u.title, u.url, u.location, u.use_avatar, u.signature, u.email_setting, u.num_posts, u.registered, u.admin_note, p.id, p.poster AS username, p.poster_id, p.poster_ip, p.poster_email, p.message, p.hide_smilies, p.posted, p.edited, p.edited_by, g.g_id, g.g_user_title, o.user_id AS is_online FROM punbb_posts AS p INNER JOIN punbb_users AS u ON u.id=p.poster_id INNER JOIN punbb_groups AS g ON g.g_id=u.group_id LEFT JOIN punbb_online AS o ON (o.user_id=u.id AND o.user_id!=1 AND o.idle=0) WHERE p.topic_id=29370 ORDER BY p.id LIMIT 0,25
0.00085	UPDATE punbb_topics SET num_views=num_views+1 WHERE id=29370
Total query time: 0.00543 s

Forum Debian Users Gang

Ogłoszenie

#1 2017-02-19 13:26:23

darko - Nowy użytkownik

Niska wydajńość po wybudzeniu.

#2 2017-02-19 13:42:02

Marek607 - Użytkownik

Re: Niska wydajńość po wybudzeniu.

#3 2017-02-19 13:42:12

ilin - Palacz

Re: Niska wydajńość po wybudzeniu.

#4 2017-02-19 13:51:11

darko - Nowy użytkownik

Re: Niska wydajńość po wybudzeniu.

Kod:

#5 2017-02-19 14:03:03

ilin - Palacz

Re: Niska wydajńość po wybudzeniu.

#6 2017-02-19 14:24:43

darko - Nowy użytkownik

Re: Niska wydajńość po wybudzeniu.

Stopka forum

Informacje debugowania