From: Andrew Morton <akpm@osdl.org>
To: CIJOML <cijoml@volny.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Bug 185] Sometimes kernel freezes sometime lists OOPS - hostap_cs
Date: Thu, 19 Oct 2006 01:44:46 -0700 [thread overview]
Message-ID: <20061019014446.36410c81.akpm@osdl.org> (raw)
In-Reply-To: <200610191012.49544.cijoml@volny.cz>
On Thu, 19 Oct 2006 10:12:49 +0200
CIJOML <cijoml@volny.cz> wrote:
> it is nsc-ircc:
>
> nsc-ircc, chip->init
> nsc-ircc, Found chip at base=0x02e
> nsc-ircc, driver loaded (Dag Brattli)
> nsc-ircc, Using dongle: HP HSDL-2300, HP HSDL-3600/HSDL-3610
Well you could try this I suppose...
--- a/drivers/net/irda/nsc-ircc.c~a
+++ a/drivers/net/irda/nsc-ircc.c
@@ -2160,7 +2160,8 @@ static int nsc_ircc_net_open(struct net_
iobase = self->io.fir_base;
- if (request_irq(self->io.irq, nsc_ircc_interrupt, 0, dev->name, dev)) {
+ if (request_irq(self->io.irq, nsc_ircc_interrupt, IRQF_SHARED,
+ dev->name, dev)) {
IRDA_WARNING("%s, unable to allocate irq=%d\n",
driver_name, self->io.irq);
return -EAGAIN;
@@ -2354,7 +2355,7 @@ static int nsc_ircc_resume(struct platfo
nsc_ircc_init_dongle_interface(self->io.fir_base, self->io.dongle_id);
if (netif_running(self->netdev)) {
- if (request_irq(self->io.irq, nsc_ircc_interrupt, 0,
+ if (request_irq(self->io.irq, nsc_ircc_interrupt, IRQF_SHARED,
self->netdev->name, self->netdev)) {
IRDA_WARNING("%s, unable to allocate irq=%d\n",
driver_name, self->io.irq);
_
Did this all work under any previous kernel? If so, which version?
It'd be useful to see the full `dmesg -s 1000000' output for both good and
bad kernels, and /proc/interrupts for the good kernel.
next prev parent reply other threads:[~2006-10-19 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 15:47 [Bug 185] Sometimes kernel freezes sometime lists OOPS - hostap_cs CIJOML
2006-10-19 6:56 ` Andrew Morton
2006-10-19 8:12 ` CIJOML
2006-10-19 8:44 ` Andrew Morton [this message]
2006-10-19 9:51 ` CIJOML
2006-10-19 13:43 ` [PATCH] account_system_vtime() should be a macro, not a function Eric Dumazet
2006-10-19 13:46 ` Andi Kleen
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=20061019014446.36410c81.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=cijoml@volny.cz \
--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