From: Jan Marek <linux@hazard.jcu.cz>
To: David Woodhouse <dwmw2@infradead.org>
Subject: Re: Cannot unlock spinlock... Was: Problem in yenta.c, 2nd edition
Date: Wed, 7 Nov 2001 11:07:02 +0100 [thread overview]
Message-ID: <20011107110702.D11351@hazard.jcu.cz> (raw)
In-Reply-To: <20011107104044.C11351@hazard.jcu.cz> <20011106123427.A11351@hazard.jcu.cz> <3BE2D37A.D32C6DB1@zip.com.au> <20011105112900.C5919@hazard.jcu.cz> <23001.1005086449@redhat.com> <11670.1005127189@redhat.com>
In-Reply-To: <11670.1005127189@redhat.com>
Hallo,
On Wed, Nov 07, 2001 at 09:59:49AM +0000, David Woodhouse wrote:
>
> linux@hazard.jcu.cz said:
> > Your hack is working for me. I got message: "IRQ storm detected on
> > IRQ 11. Disabling"
>
> > and everythink works OK. Spinlock was unlocked, procedure setup_irq()
> > ended and PCMCIA package works fine...
>
> > It is possible to add your patch to the kernel?
>
> Absolutely not. In 2.5, we may have some code to deal with IRQ storms, but
> certainly not like that.
OK... But shall I apply your patch on every kernel while not
exist 2.5 kernel tree?
>
> > But I don't know, what device asserted IRQ 11 to start the IRQ storm..
>
> What other PCI devices claim to be on IRQ 11? Do you have ACPI enabled (in
> the BIOS and/or in Linux)?
I have ACPI enabled and I'm attaching my lspci -vvv... Thank you
very much...
> --
> dwmw2
Sincerely
Jan Marek
--
Ing. Jan Marek
University of South Bohemia
Academic Computer Centre
Phone: +420-38-7772080
next prev parent reply other threads:[~2001-11-07 10:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3BE2D37A.D32C6DB1@zip.com.au>
2001-11-05 10:29 ` [Fwd: Re: Problem in yenta.c, 2nd edition] Jan Marek
2001-11-06 11:34 ` Cannot unlock spinlock... Was: Problem in yenta.c, 2nd edition Jan Marek
2001-11-06 22:40 ` David Woodhouse
2001-11-07 9:40 ` Jan Marek
2001-11-07 9:59 ` David Woodhouse
2001-11-07 10:07 ` Jan Marek [this message]
2001-11-07 10:10 ` Jan Marek
2001-11-07 10:30 ` Alan Cox
2001-11-07 10:29 ` David Woodhouse
2001-11-07 10:47 ` Alan Cox
2001-11-07 10:55 ` Jan Marek
2001-11-07 15:04 ` Doug McNaught
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=20011107110702.D11351@hazard.jcu.cz \
--to=linux@hazard.jcu.cz \
--cc=dwmw2@infradead.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
all inboxes | Powered by JetHome®