Unhandled interrupt 0, disabled

Unhandled interrupt 0, disabled

[Steve.Ferri]

All:

I have run different kernel versions (2.4.7 to 2.4.15) on an the 8260
based card we are using.  After the
kernel has been loaded, I always seem to see the message "Unhandled
interrupt 0, disabled".
It doesn't always occur at the same time.  I've seen the message right
after the kernel has finished
booting, after i started my application, or initialized some drivers.  It
occurs only once.

Looking at the 8260 manual IRQ 0 is described as "Error (No Interrupt)".
Looking at the code in irq.c
this event doesn't hurt anything, and most likely can be ignored.  I just
want to understand
how this interrupt vector is getting to the irq_distacher.  Also, should I
be concerned about this
or should I just continue to ignore the event ?

Also this is marked in the /proc/interrupts  file under the BAD: entry
(counted as a spurious interrupt)

              CPU0
 13:       8629            8260 SIU   Edge      timer_irq
 19:          0                8260 SIU   Edge      qfalc_irq
 21:          1                8260 SIU   Edge      pci_irq
 33:       25438          8260 SIU   Edge      fenet
 36:       29585934   8260 SIU   Edge      mcc1_irq
BAD:          1

Perhaps this just always occurs in 8260's after boot ?

Regards,
Steve

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Steve Ferri                         Radisys Corporation
                                               520 Fellowship Rd.
                                               Suite C-304
www.radisys.com             Mt. Laurel, NJ 08054

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Unhandled interrupt 0, disabled

[Jean-Denis Boyer]

Mr. Ferri,

I've started a thread of discussion about that a couple of weeks ago, but I
didn't have a satisfying answer. However, I've proposed a fix which seems to
work. I think I should go further with Motorola about that problem. Can you
take a look at it and tell me if it helps? Also, can you tell me which
processor mask you are running on?

Look at
http://lists.linuxppc.org/linuxppc-embedded/200204/threads2.html#00074

The thread is titled:
  8260 - Spurious interrupt when calling __sti()

--------------------------------------------
 Jean-Denis Boyer, B.Eng., System Architect
 Mediatrix Telecom Inc.
 4229 Garlock Street
 Sherbrooke (Québec)
 J1L 2C8  CANADA
 (819)829-8749 x241
--------------------------------------------

> -----Original Message-----
> From: Steve.Ferri@radisys.com [mailto:Steve.Ferri@radisys.com]
> Sent: 3 mai, 2002 09:04
> To: linuxppc-embedded@lists.linuxppc.org
> Subject: Unhandled interrupt 0, disabled
>
>
>
> All:
>
> I have run different kernel versions (2.4.7 to 2.4.15) on an the 8260
> based card we are using.  After the
> kernel has been loaded, I always seem to see the message "Unhandled
> interrupt 0, disabled".
> It doesn't always occur at the same time.  I've seen the message right
> after the kernel has finished
> booting, after i started my application, or initialized some
> drivers.  It
> occurs only once.
>
> Looking at the 8260 manual IRQ 0 is described as "Error (No
> Interrupt)".
> Looking at the code in irq.c
> this event doesn't hurt anything, and most likely can be
> ignored.  I just
> want to understand
> how this interrupt vector is getting to the irq_distacher.
> Also, should I
> be concerned about this
> or should I just continue to ignore the event ?
>
> Also this is marked in the /proc/interrupts  file under the BAD: entry
> (counted as a spurious interrupt)
>
>               CPU0
>  13:       8629            8260 SIU   Edge      timer_irq
>  19:          0                8260 SIU   Edge      qfalc_irq
>  21:          1                8260 SIU   Edge      pci_irq
>  33:       25438          8260 SIU   Edge      fenet
>  36:       29585934   8260 SIU   Edge      mcc1_irq
> BAD:          1
>
> Perhaps this just always occurs in 8260's after boot ?
>
> Regards,
> Steve
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Steve Ferri                         Radisys Corporation
>                                                520 Fellowship Rd.
>                                                Suite C-304
> www.radisys.com             Mt. Laurel, NJ 08054
>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Unhandled interrupt 0, disabled

[Jean-Denis Boyer]

Mr. Ferri,

> Which fix are you standing behind your __sti()
> fix using the sync or the 2.4.18 patch ?

Just put the 'sync' in __sti().
It seems to fix the problem on both 2.4.10 and 2.4.18,
which are the versions I have tested.

> I am using the B.3 version of the 8260
Thank you for the information!

--------------------------------------------
 Jean-Denis Boyer, B.Eng., System Architect
 Mediatrix Telecom Inc.
 4229 Garlock Street
 Sherbrooke (Québec)
 J1L 2C8  CANADA
 (819)829-8749 x241
--------------------------------------------

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Unhandled interrupt 0, disabled

[Allen Curtis]

> Just put the 'sync' in __sti().
> It seems to fix the problem on both 2.4.10 and 2.4.18,
> which are the versions I have tested.
>
> > I am using the B.3 version of the 8260

I know that this is unrelated but could you confirm whether B.3 and higher
fixes the CP hang problem when using an external PCI controller such as the
PowerSpan.

Thanks


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Unhandled interrupt 0, disabled

[Steve.Ferri]

Allen,

We are using a PMC board that has the B.3 version of the 8260 along with
the
Tundra PowerSpan 420.  I haven't seen any CP hang problems
with regards the on board PCI controller.  The PowerSpan is connected to
the
8260's external interrupt line IRQ3.  We are using a custom PCI driver
for host to daughter card communication, where the 8260 card is acting as
a daughter card.

Now working with the MCC devices on the B.3 version of the 8260 is another
story...

Regards,
Steve

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Steve Ferri                         Radisys Corporation
Tel: 856 642-9229 x239  520 Fellowship Rd.
Fax: 856 642-0252            Suite C-304
www.radisys.com             Mt. Laurel, NJ 08054







"Allen Curtis" <acurtis@onz.com>
Sent by: owner-linuxppc-embedded@lists.linuxppc.org
05/03/02 11:31 AM
Please respond to acurtis


        To:     "Jean-Denis Boyer" <jdboyer@mediatrix.com>, <Steve.Ferri@radisys.com>
        cc:     <linuxppc-embedded@lists.linuxppc.org>
        Subject:        RE: Unhandled interrupt 0, disabled



> Just put the 'sync' in __sti().
> It seems to fix the problem on both 2.4.10 and 2.4.18,
> which are the versions I have tested.
>
> > I am using the B.3 version of the 8260

I know that this is unrelated but could you confirm whether B.3 and higher
fixes the CP hang problem when using an external PCI controller such as
the
PowerSpan.

Thanks


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/