public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alexey Starikovskiy <astarikovskiy@suse.de>
Cc: Tim Elliott <tle@holymonkey.com>,
	Guillaume Chazarain <guichaz@gmail.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	lenb@kernel.org
Subject: Re: ACPI regression in 2.6.25-rc6 (function keys stop working)
Date: Wed, 19 Mar 2008 23:10:17 +0100	[thread overview]
Message-ID: <200803192310.18692.rjw@sisk.pl> (raw)
In-Reply-To: <47E01C86.9080306@suse.de>

On Tuesday, 18 of March 2008, Alexey Starikovskiy wrote:
> Tim Elliott wrote:
> > I am seeing the same problem on my Lenovo 3000 v100. The function keys
> > stopped working.
> > 
> > tim@tim-len:~$ cat /proc/interrupts
> >            CPU0       CPU1
> >   0:     164105          0   IO-APIC-edge      timer
> >   1:      12560          0   IO-APIC-edge      i8042
> >   9:          6          0   IO-APIC-fasteoi   acpi
> >  12:     117534          0   IO-APIC-edge      i8042
> >  14:         51          0   IO-APIC-edge      ide0
> >  16:         31          0   IO-APIC-fasteoi   uhci_hcd:usb4,
> > i915@pci:0000:00:02.0
> >  18:     121892          0   IO-APIC-fasteoi   uhci_hcd:usb3, iwl3945
> >  19:      36197          0   IO-APIC-fasteoi   uhci_hcd:usb2, ahci
> >  20:       7931          0   IO-APIC-fasteoi   eth0
> >  22:      11071          0   IO-APIC-fasteoi   sdhc0:slot0, HDA Intel
> >  23:          5          0   IO-APIC-fasteoi   uhci_hcd:usb1, ehci_hcd:usb5
> > NMI:          0          0   Non-maskable interrupts
> > LOC:      11296      73879   Local timer interrupts
> > RES:      23199      49164   Rescheduling interrupts
> > CAL:        297      27033   function call interrupts
> > TLB:        838       1286   TLB shootdowns
> > TRM:          0          0   Thermal event interrupts
> > THR:          0          0   Threshold APIC interrupts
> > SPU:          0          0   Spurious interrupts
> > ERR:          0
> > 
> > The problem goes away when reverting 2c81ce4c9c37b910210f2640c28e98a0c398dc26
> > 
> > Reverting the above and applying the patch in comment #38 of bug #9998
> > also works (http://bugzilla.kernel.org/show_bug.cgi?id=9998).
> reverting the above and patch in comment #38 of #9998 are the same thing.
> I am really interested if after revert (or application of #38) you notice a
> difference in interrupt count before and after applying #37 from #9998.

What is the relationship between this problem and bug #10279?

Rafael

  reply	other threads:[~2008-03-19 22:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18  0:13 ACPI regression in 2.6.25-rc6 (function keys stop working) Guillaume Chazarain
2008-03-18 10:22 ` Alexey Starikovskiy
2008-03-18 13:17 ` Alexey Starikovskiy
2008-03-18 17:23   ` Tim Elliott
2008-03-18 19:48     ` Alexey Starikovskiy
2008-03-19 22:10       ` Rafael J. Wysocki [this message]
2008-03-18 23:29   ` Guillaume Chazarain
2008-03-18 23:40     ` Alexey Starikovskiy
2008-03-18 23:53     ` Alexey Starikovskiy
2008-03-19  1:14     ` Alexey Starikovskiy

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=200803192310.18692.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=astarikovskiy@suse.de \
    --cc=guichaz@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tle@holymonkey.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox