Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Zhang Fuxin <fxzhang@ict.ac.cn>
To: Scott A McConnell <samcconn@cotw.com>
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: MIPS, i8259 and spurious interrupts.
Date: Tue, 26 Feb 2002 14:50:9 +0800	[thread overview]
Message-ID: <200202260752.g1Q7qP904669@oss.sgi.com> (raw)

hi,


>/************************************************************************************/
>/* Why am I not returning from the following
>call?                                  */
>/************************************************************************************/
>
>	printk("*** SP 1 irq: %d***\n", irq);
>	if (i8259A_irq_real(irq))
>		/*
>		 * oops, the IRQ _is_ in service according to the
>		 * 8259A - not spurious, go handle it.
>		 */
>	printk("*** SP 2 ***\n");
>		goto handle_real_irq;
do you really mean it? the goto is unconditional now?
but your output susgest that i8259A_irq_real never return true
>
>	{
>		static int spurious_irq_mask = 0;
>
>	printk("*** SP 3 ***\n");
>
>		/*
>		 * At this point we can be sure the IRQ is spurious,
>		 * lets ACK and report it. [once per IRQ]
>		 */
>	printk("*** SP 4 ***\n");
>
>		if (!(spurious_irq_mask & irqmask)) {
>			printk("spurious 8259A interrupt: IRQ%d.\n", irq);
>			spurious_irq_mask |= irqmask;
>		}
>	printk("*** SP 5 ***\n");
>
>		irq_err_count++;
>		/*
>		 * Theoretically we do not have to handle this IRQ,
>		 * but in Linux this does not cause problems and is
>		 * simpler for us.
>		 */
>	printk("*** SP 6 ***\n");
>
>		goto handle_real_irq;
>	}
>}
>
>
>Thanks in advance for any advice...
>
>-- 
>Scott A. McConnell

Regards
            Zhang Fuxin
            fxzhang@ict.ac.cn

             reply	other threads:[~2002-02-26  7:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26  6:50 Zhang Fuxin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-25 19:50 MIPS, i8259 and spurious interrupts Scott A McConnell
2002-02-26 10:49 ` Dominic Sweetman
2002-02-26 11:10   ` Alan Cox
2002-02-26 11:10     ` Alan Cox

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=200202260752.g1Q7qP904669@oss.sgi.com \
    --to=fxzhang@ict.ac.cn \
    --cc=linux-mips@oss.sgi.com \
    --cc=samcconn@cotw.com \
    /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