mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Marek <linux@hazard.jcu.cz>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: dwmw2@infradead.org
Subject: Re: Cannot unlock spinlock... Was: Problem in yenta.c, 2nd edition
Date: Wed, 7 Nov 2001 10:40:44 +0100	[thread overview]
Message-ID: <20011107104044.C11351@hazard.jcu.cz> (raw)
In-Reply-To: <20011106123427.A11351@hazard.jcu.cz> <3BE2D37A.D32C6DB1@zip.com.au> <20011105112900.C5919@hazard.jcu.cz> <23001.1005086449@redhat.com>
In-Reply-To: <23001.1005086449@redhat.com>

Hallo l-k,

On Tue, Nov 06, 2001 at 10:40:49PM +0000, David Woodhouse wrote:
> 
> linux@hazard.jcu.cz said:
> >  The last message I got from kernel is:  request_irq: desc->handler->
> > startup(irq)
> 
> > Then problem is in the spin_unlock_irqrestore()???
> 
> > Any ideas, recomendations, suggestions?
> 
> It's dying in an IRQ storm. Something is permanently asserting IRQ 11, and 
> unless you can work out what's doing it and make it stop, the machine will 
> die whenever you enable that IRQ.
> 
> Try this hack, just to make sure:

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?

But I don't know, what device asserted IRQ 11 to start the IRQ
storm... When I was in the function setup_irq(), I installed the
first routine to work with IRQ 11 in its IRQ queue...

Or maybe will be safe to disable concrete IRQ, when is installed
a new handler for it?

I'm sorry, I'm not kernel programmer at all, I still thinking
about it... Maybe will be my think usefull for you...

> 
> --
> dwmw2

Sincerely
Jan Marek
-- 
Ing. Jan Marek
University of South Bohemia
Academic Computer Centre
Phone: +420-38-7772080

  reply	other threads:[~2001-11-07  9:42 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 [this message]
2001-11-07  9:59     ` David Woodhouse
2001-11-07 10:07       ` Jan Marek
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=20011107104044.C11351@hazard.jcu.cz \
    --to=linux@hazard.jcu.cz \
    --cc=dwmw2@infradead.org \
    --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

all inboxes | Powered by JetHome®