From: Paul Rolland <rol@as2917.net>
To: Tejun Heo <htejun@gmail.com>
Cc: David Newall <david@davidnewall.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
rol@witbe.net
Subject: Re: 2.6.23-rc7 - _random_ IRQ23 : nobody cared
Date: Thu, 27 Sep 2007 08:05:51 +0200 [thread overview]
Message-ID: <20070927080551.424e90b9@tux.DEF.witbe.net> (raw)
In-Reply-To: <46FAFF7A.5070208@gmail.com>
Hi Tejun,
On Thu, 27 Sep 2007 09:55:22 +0900
Tejun Heo <htejun@gmail.com> wrote:
> Paul Rolland wrote:
> > Hi David,
> >
> > On Mon, 24 Sep 2007 23:56:59 +0930
> > David Newall <david@davidnewall.com> wrote:
> >
> >> Paul Rolland "(???????) wrote:
> >>> Hell, IRQ 23 is shared between libata and my modem !!!
> >>>
> >> Tried using the modem?
> >
> Can you change driver load order such that the driver for the modem is
> loaded first?
As I said, it's not possible, because :
- the modem driver is an out-kernel one, so I have to wait the end of the
boot process so that it can be loaded,
- libata on IRQ23 is the one taking care of my disks, and I suspect it
quite hard to install a modem driver before having the disk driver
installed.
I was thinking of delaying the disabling of the IRQ, which is basically the
other part of the problem (the first part being that spurious IRQ from the
modem). If it is possible to do that long enough for the modem driver to be
loaded, then the "IRQ xx : nobody cared" becomes an informational message
during the boot process, and then it vanishes, leaving a perfectly working
machine.
I suspect something in note_interrupt that would do (totally
untested, just thinking loudly) :
/* Allow some delay to complete boot process before
* killing an IRQ. This allow some modules to be
* loaded before we decide the IRQ will not be handled.
*/
if (jiffies > 120*HZ) {
/*
* Now kill the IRQ
*/
printk(KERN_EMERG "Disabling IRQ #%d\n", irq);
desc->status |= IRQ_DISABLED;
desc->depth = 1;
desc->chip->disable(irq);
}
I'll try that this week-end, but if someone has an opinion about it, I'll
be glad to know :)
Regards,
Paul
next prev parent reply other threads:[~2007-09-27 6:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 6:33 2.6.23-rc7 - _random_ IRQ23 : nobody cared Paul Rolland
2007-09-24 14:26 ` David Newall
2007-09-25 7:00 ` Paul Rolland
2007-09-27 0:55 ` Tejun Heo
2007-09-27 6:05 ` Paul Rolland [this message]
2007-09-27 9:04 ` Benjamin Herrenschmidt
2007-09-27 10:05 ` Paul Rolland
2007-09-27 22:27 ` Benjamin Herrenschmidt
2007-09-28 6:30 ` Paul Rolland
2007-09-28 9:55 ` Tejun Heo
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=20070927080551.424e90b9@tux.DEF.witbe.net \
--to=rol@as2917.net \
--cc=david@davidnewall.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rol@witbe.net \
/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).