All of lore.kernel.org
 help / color / mirror / Atom feed
From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "Dave Jones" <davej@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Ondemand/Conservative not working with 2.6.18
Date: Mon, 16 Oct 2006 23:29:17 +0300	[thread overview]
Message-ID: <200610162329.17482.caglar@pardus.org.tr> (raw)
In-Reply-To: <EB12A50964762B4D8111D55B764A8454BA3D91@scsmsx413.amr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]

16 Eki 2006 Pts 16:08 tarihinde, Pallipadi, Venkatesh şunları yazmıştı: 
> Sorry for the delayed response. This is still very mysterious to me..
>
> Do you see anything interesting in dmesg after you try this ac adapter
> unplug and plug back routine? Can you send me the dmesg. Better still open
> a bugzilla at bugme.osdl.org and stick the dmesg and acpidump there.

No, nothing interested and i filled a bug [1] with all related info

> One possible reason for this is, somehow idle statistics is getting all
> wrong and ondemand thinks CPU is busy, even though it is idle. I have seen
> this happening earlier when there are issues with local APIC interrupts in
> deep C-states on dual core systems. But, here it is a single core CPU.
> Right? Can you also get the output of #cat /proc/interrupts; sleep 10; cat
> /proc/interrupts
> On your system when ondemand is not working and when it is working (After
> your unplug-plug workaround.

Hmm top show something weird;

Tasks:  39 total,   1 running,  38 sleeping,   0 stopped,   0 zombie
Cpu(s): 32.4%us, 12.4%sy,  0.0%ni, 41.1%id, 13.0%wa,  0.4%hi,  0.6%si,  0.0%st

There were nothing runs right that time but top reports only ~%40 idle [full 
log attached to bug]

[1] http://bugme.osdl.org/show_bug.cgi?id=7376
-- 
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/

Linux is like living in a teepee. No Windows, no Gates and an Apache in house!

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-10-16 20:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16 13:08 Ondemand/Conservative not working with 2.6.18 Pallipadi, Venkatesh
2006-10-16 20:29 ` S.Çağlar Onur [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-11 19:00 Pallipadi, Venkatesh
2006-10-11 19:08 ` S.Çağlar Onur
2006-10-11 19:38 ` S.Çağlar Onur
2006-10-11 19:39 ` S.Çağlar Onur
2006-10-13 18:33 ` S.Çağlar Onur
2006-10-09 23:35 Pallipadi, Venkatesh
2006-10-10 20:54 ` S.Çağlar Onur
2006-10-04 13:33 S.Çağlar Onur
2006-10-09 21:52 ` S.Çağlar Onur

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200610162329.17482.caglar@pardus.org.tr \
    --to=caglar@pardus.org.tr \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.