All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Alexey Starikovskiy <astarikovskiy@suse.de>
Cc: linux-kernel@vger.kernel.org, lenb@kernel.org
Subject: Re: Reading EeePC900 battery info causes stalls
Date: Sat, 20 Sep 2008 14:30:51 +0100	[thread overview]
Message-ID: <48D4FB0B.2060208@yahoo.com> (raw)
In-Reply-To: <48D4F57C.5010902@suse.de>

Alexey Starikovskiy wrote:
> Sitsofe Wheeler wrote:
>> Alexey Starikovskiy wrote:
>>> Could you cat /proc/interrupts ?
>>
>>            CPU0
>>   0:     106942   IO-APIC-edge      timer
>>   1:        426   IO-APIC-edge      i8042
>>   8:         41   IO-APIC-edge      rtc0
>>   9:      27346   IO-APIC-fasteoi   acpi
>>  12:       6840   IO-APIC-edge      i8042
>>  14:          0   IO-APIC-edge      ata_piix
>>  15:        203   IO-APIC-edge      ata_piix
>>  16:      92357   IO-APIC-fasteoi   uhci_hcd:usb5, HDA Intel, 
>> i915@pci:0000:00:02.0
>>  18:      38195   IO-APIC-fasteoi   ath, uhci_hcd:usb4
>>  19:          0   IO-APIC-fasteoi   uhci_hcd:usb3
>>  23:      25150   IO-APIC-fasteoi   ehci_hcd:usb1, uhci_hcd:usb2
>> NMI:          0   Non-maskable interrupts
>> LOC:     142112   Local timer interrupts
>> TRM:          0   Thermal event interrupts
>> SPU:          0   Spurious interrupts
>> ERR:          0
>> MIS:          0
> Could you please try following patch on top?

Unfortunately it still stalls (hotkeys still seem to be working 
correctly though).

-- 
Sitsofe | http://sucs.org/~sits/

  reply	other threads:[~2008-09-20 13:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.aea4e10hJLpVS/qr4bumSa5e9C0@ifi.uio.no>
     [not found] ` <fa.uDmoMIWw4thxpZxpYeSIpVJhAOo@ifi.uio.no>
     [not found]   ` <fa.RIMmQqN9ybFSKBqOk9Gxi/mOeB4@ifi.uio.no>
     [not found]     ` <fa.XLGLzP+T4fm9CkeATkS1VL/Yz4Q@ifi.uio.no>
     [not found]       ` <fa.z8sKLpwDO3qQ15ZJIm152YEty4I@ifi.uio.no>
     [not found]         ` <fa.KyW7dWWjiSFnFxwdZZLurmVn8qA@ifi.uio.no>
2008-09-20 10:10           ` Reading EeePC900 battery info causes stalls (was Re: How how latent should non-preemptive scheduling be?) Sitsofe Wheeler
2008-09-20 10:25             ` Alexey Starikovskiy
2008-09-20 10:51               ` Sitsofe Wheeler
2008-09-20 10:55                 ` Reading EeePC900 battery info causes stalls Sitsofe Wheeler
2008-09-20 11:14                   ` Alexey Starikovskiy
2008-09-20 11:23                     ` Sitsofe Wheeler
2008-09-20 11:41                       ` Sitsofe Wheeler
2008-09-20 12:34                         ` Alexey Starikovskiy
2008-09-20 12:50                           ` Sitsofe Wheeler
2008-09-20 13:07                       ` Alexey Starikovskiy
2008-09-20 13:30                         ` Sitsofe Wheeler [this message]
2008-09-20 13:59             ` Reading EeePC900 battery info causes stalls (was Re: How how latent should non-preemptive scheduling be?) Steven Rostedt
2008-09-20 14:11               ` Sitsofe Wheeler
2008-09-20 14:37                 ` Steven Rostedt
2008-09-20 17:16                   ` Reading EeePC900 battery info causes stalls Sitsofe Wheeler
2008-09-20 21:53                     ` Steven Rostedt
2008-09-20 23:18                       ` Sitsofe Wheeler
2008-09-21  7:09                         ` Ingo Molnar
2008-09-22  6:24                       ` Sitsofe Wheeler
2008-09-24 17:52 Sitsofe Wheeler
2008-09-25  8:47 ` Alexey Starikovskiy
2008-09-25  9:35   ` Sitsofe Wheeler
2008-09-25  9:36   ` Sitsofe Wheeler
2008-09-25  9:54     ` Alexey Starikovskiy
2008-09-25 11:07       ` Alexey Starikovskiy
2008-09-25 11:56         ` Sitsofe Wheeler
2008-09-25 12:01           ` Alexey Starikovskiy
2008-09-25 14:57             ` Alexey Starikovskiy
2008-09-25 17:30               ` Sitsofe Wheeler
2008-09-25 11:17       ` Sitsofe Wheeler

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=48D4FB0B.2060208@yahoo.com \
    --to=sitsofe@yahoo.com \
    --cc=astarikovskiy@suse.de \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.