public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: florin@iucha.net (Florin Iucha)
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
	Dominik Brodowski <linux@dominikbrodowski.net>
Subject: Re: pcmcia oops on 2.6.17-rc[12]
Date: Sun, 23 Apr 2006 19:46:06 -0500	[thread overview]
Message-ID: <20060424004606.GF8896@iucha.net> (raw)
In-Reply-To: <20060423150206.546b7483.akpm@osdl.org>

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

On Sun, Apr 23, 2006 at 03:02:06PM -0700, Andrew Morton wrote:
> florin@iucha.net (Florin Iucha) wrote:
> > With 2.6.17-rc[12] I get the following oops:
>
> It's actually not an oops - it's a warning, telling us that i82365 is
> requesting an IRQ in non-sharing mode, but there's already a handler
> registered for that IRQ (which might or might not be shareable).
>
> Your machine should otherwise continue to work OK.  Is that the case?

Yes, it works fine - it just looked scary ;)

> Anyway.  We need to either a) make i82365 better-behaved or b) remove the
> warning or c) allow callers to suppress the warning (SA_PROBEIRQ?).
> 
> I think c) - the warning can help find bugs.
> 
> 
> 
> From: Andrew Morton <akpm@osdl.org>
> 
> - Add new SA_PROBEIRQ which suppresses the new sharing-mismatch warning. 
>   Some drivers like to use request_irq() to find an unused interrupt slot.
> 
> - Use it in i82365.c
> 
> - Kill unused SA_PROBE.

[With the fix suggested by Randy] it is all quiet now.

Thanks,
florin

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

  parent reply	other threads:[~2006-04-24  0:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-23 19:22 pcmcia oops on 2.6.17-rc[12] Florin Iucha
2006-04-23 22:02 ` Andrew Morton
2006-04-23 22:15   ` Randy.Dunlap
2006-04-24  0:46   ` Florin Iucha [this message]
2006-05-08 14:56   ` Andreas Mohr
2006-05-08 15:43     ` Andrew Morton
2006-05-08 16:34       ` Russell King
2006-05-15 22:07         ` Alan Cox
2006-05-15 22:00           ` Russell King
2006-05-18 11:10             ` Russell King
2006-05-15 22:02           ` Linus Torvalds
2006-05-15 23:00             ` Alan Cox
2006-05-15 23:37               ` Linus Torvalds
2006-05-15 23:52                 ` Linus Torvalds
2006-05-16  0:17                   ` Alan Cox
2006-05-16  0:18                     ` Linus Torvalds
2006-05-16  1:18                       ` Alan Cox
2006-05-16 15:16                 ` Alan Cox
2006-05-22 11:50               ` Rogier Wolff
2006-05-22 12:10                 ` Alan Cox
2006-05-22 21:27                   ` Rogier Wolff
2006-05-22 22:38                     ` Alan Cox
2006-06-02 19:09                   ` Russell King
2006-05-22 15:06                 ` Linus Torvalds

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=20060424004606.GF8896@iucha.net \
    --to=florin@iucha.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=torvalds@osdl.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