linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stelian Pop <stelian@popies.net>
To: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: OUPS 2.5.69-bk19 sonypi irq 11: nobody cared!
Date: Mon, 2 Jun 2003 10:10:45 +0200	[thread overview]
Message-ID: <20030602081045.GC12831@deep-space-9.dsnet> (raw)
In-Reply-To: <1053971418.2003.13.camel@nalesnik.localhost>

On Mon, May 26, 2003 at 06:50:36PM +0100, Grzegorz Jaskiewicz wrote:

> irq 11: nobody cared!
> 
> Call Trace:
[...]
>  [<c790c8d0>] sonypi_irq+0x0/0x2a0 [sonypi]
>  [<c790fd00>] +0x0/0x200 [sonypi]
>  [<c030206f>] pci_find_device+0x2f/0x40
>  [<c790fd00>] +0x0/0x200 [sonypi]
>  [<c78fe030>] +0x30/0x3b [sonypi]
>  [<c013509f>] sys_init_module+0xff/0x210
>  [<c790fd00>] +0x0/0x200 [sonypi]
>  [<c010b21b>] syscall_call+0x7/0xb

I have been away for a while, moving to a new house etc...

Anyway, the sonypi messages appear because of the new irq infrastructure
Linus introduced a few weeks ago. Using this infrastructure a driver can
tell if he really handled the irq or not.

The problem with the sonypi driver is that it only knows about a 
limited set of events (button presses, battery events, lid events etc),
and any event not referenced in the sonypi source will give you the
backtrace you saw.

I intend to force the sonypi driver to return IRQ_HANDLED every time
he receives an event (because it does anyway print a warning message
when it happens), but this code has not reached Linus yet.

Stelian.
-- 
Stelian Pop <stelian@popies.net>

  reply	other threads:[~2003-06-02  7:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-26 17:50 OUPS 2.5.69-bk19 sonypi irq 11: nobody cared! Grzegorz Jaskiewicz
2003-06-02  8:10 ` Stelian Pop [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-26 17:50 Grzegorz Jaskiewicz

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=20030602081045.GC12831@deep-space-9.dsnet \
    --to=stelian@popies.net \
    --cc=gj@pointblue.com.pl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).